Hi all
I am opening up this Q&A thread as extension to my ROM threads, for the simple reason that ever since there is a limitation preventing new users from posting in development threads, I get flooded with PM's. So I intent to move any Q&A, help requests, as well as free and open discussions between users here.
Since the A750 and A789 are so similar, and I put the same stuff in them, I extent both into this one Q&A thread, and in fact, much of it knowledge applies to other Lenovo's like the P700, P700i, S880, A660 which are again very similar and I even use them as basis of my ROM.
Also, I am not intending to be topic police. Like in my other threads, I do not mind if you guys share knowledge about APKHOT or Smileyvvv or Etotalk ROM. As long as it is helpful. Also, I may not always reply myself, so feel free to help each other.
Link to the original threads:
[ROM][2012.xx.xx] Lenovo A750 custom ROM (GB&ICS). <last page>
[ROM][2012.xx.xx] Lenovo A789,P700i,A660 factory&custom ROM (ICS). <last page>
Other related threads (not all mine):
CWM flashing tutorial (update using recovery)
MT6575 flashing tutorial (update using flash utility
Lenovo Original recovery tutorial
[SCRIPTS] Unpack / repack MT65xx boot.img, recovery.img or logo.bin
[REF] Unpacking and repacking stock rom .img files
[UTIL][APP]Lenovo Security / LeSec app (anti-virus/spam/theft/firewall)
[TOOL][TUT]Backup and Restore Mediatek based phone's IMEI
How to DIY : Self root/gapps/playstore/locationfix/clean my ROM
This is a guide on how to root & cleanup your China ROM yourself. It will probably work on all ICS China phones. But it requires & starts with the availability of a recovery image for your phone
There are in fact a few steps:
- Get a proper recovery image for your phone.
- Root it by installing Chainfire's root package
- Install Google GMS ('GAPPS') to get Play Store and Localisation to work
And optionally
- Install Mobile UncleToolset
- Install an extra small fix with location services
- Install an extra small fix with latest APN list
- Install an extra fix to remove well known Chinese system apps
Recovery image
The Recovery Image allows you to boot into an alternative small Linux that you can then use to update the main Android. Updates usually come in "update.zip" scripted files. And the recovery has some other utilities like backup or wipe the entire phone. Getting a working recovery for your phone is step number one, because if you have a recovery, you can do everything else.
To check if you already have a recovery: Well, try to boot into it. The boot sequence may vary with the phone, but on MediaTek phones it is usually to replace the battery and then press&hold both volume buttons while powering up. I have seen it where you need to actually press the power button a split second before pressing both volume buttons. Try a few times, replacing the battery each time.
If you get to a screen that reads CWMR or CWMR Touch (short for ClockWorkModRecovery), you are all set and can continue with rooting. CWMR it is the most common open recovery image. If your recovery is closed, then you need to search the web for a working recovery for your specific model. Each brand and model needs its own recovery, because screen drivers, buttons and partition tables may differ.
Search the web is the best advise. Search wide and search deep. If you cannot find any recovery, then see if you can find a full ROM for your phone. If you have a working ROM image, then there are people on XDA that can make a recovery for you, but typically you need to show/prove that you have really tried to find one yourself.
Flashing a recovery
If you do find a recovery, that you suspect is the correct one for your ROM, then comes the scary part: Flashing the recovery to the phone.
This paragraph is specific to Mediatek based phones. On different hardware you also need a recovery, and once you have a recovery, you can use the other parts of this post, but how to flash other hardware, I do not know, sorry
Flashing using the flash tool is scary to new users. Because new users suspect that if they mess it up, the phone dies. And this is correct! But if you only flash the recovery.img part, you should be fairly safe. Read this manual on flashing. Getting the USB driver installed is sometimes a bit tricky, you may also want to read post #21 and post #25 for help.
I have seen several people asking 'where to find the scatter file'. Well, it comes with the ROM you want to flash. If your ROM file does not come with a scatter file, then is not a ROM file that can be flashed with the flash utility, but with an open recovery.
Rooting
Once you have a working recovery, the rest is simple. For rooting, simply install (from inside the recovery) chainfire's "CMW installable ZIP"
Link to his post: (ignore his big red 'requires root' warning). The file you need is labeled "CWM installable ZIP" at the bottom. Direct link to the file you need to install via recovery update.zip
This usually works by putting the zip file on the SD card (its name can be anything, though for some limited recoveries it sometimes must be named 'update.zip'), booting into recovery, and selecting the zip file to update.
Google GMS (Market/Play Store, Location, etc)
Simply install the latest Google Mobile Services (better known as GAPPS) from CyanogenMod V9. This is their explaining wiki from CyanogenMod
The file you need is called gapps-ics-20120429-signed.zip for ICS and gapps-jb-20121212-signed.zip for JB and can be found here. You probably also want to wipe your cache partition after doing this.
Mobile Uncle toolset
Just install this program apk (so not through the recovery, just install it normally). Or search the web for the latest one.
Fix location services
If location services does not work, do apply Google GMS (GAPPS) above. If it still does not work, it may be because the phone is programmed to use Chinese location services. This patch will tell it to use GMS. The patch will apply, and probably even work, on all ICS phones. But was originally made&tested on a Lenovo A750 ICS. Its called V1.3 because many people have downloaded the A750 v1.3 patch and used it on many MT6575 phones. It is still the same patch, except the update.zip is tweaked to work on any ICS phone, not only MT6575 ones.
Sometimes you also need to go into MobileUncle tool, the MTK Engineer mode, and in location settings. Depending on your exact model, somewhere in there is a NetLoc or NetLocation and a GeoCoding setting, with options of MEDIATEK and GOOGLE. Ensure they are set to GOOGLE.
After messing with location settings, it is best to also wipe cache.
Fix APN list (or My 3G does not connect!)
You can always add your own APN (Access Point Names) from the settings menu. Just add your own, and select that over the pre-build one. But this package will update with the latest list as maintained by CyanogenMod 9. The update.zip was made in such a way it should work on all ICS phones, Mediatek or other.
Clean well known Chinese system apps
<patch still coming>
==========================================
List of known recovery images for Mediatek Flash tool:
Lenovo A750 : 592zn : See also this post #607, nandroid backup does not work.
Lenovo A789 : 592zn or APKHOT
Lenovo P700i : My own, based on APKHOT with CWM.
Lenovo P700 : My own, based on CWMT / 592zn. nandroid backup will not work.
Lenovo A660 : My own, based on APKHOT with CWM
Lenovo S560 : My own, based on APKHOT with CWM (as yet untested)
Additional Recovery Images in this post.
If you feel you searched all over the web, and could not find a recovery for your model, and you next feel you should ask me or one of the other people on XDA to make you one (which I am not encouraging), than please be aware we need at least a 'standard ROM' for your phone to start from. Without it, I can do nothing. So go back out there, and find a standard ROM, does not matter what language, as long as it is for your specific phone model and known to work.
Also, as an extra warning : If you are flashing, and you experiment with 'suspicious' ROM sources, *never ever* flash the preloader, mbr, ebr uboot. Only flash those from a trusted source and if they belong to your exact brand and model phone.
One more reserved
lolo250612 said:
Hello from France,
Just a little message to thank you very much for your very useful "Lenovo A789 factory&custom ROM (ICS)" thread. I have just bought a A789 from etotalk, and your posts really help to master the beast.
I can't participate to the thread because I am a new member and consequently can't post message to this development thread. And this very sad, because I have discovered a shortcoming of this phone. Apparently, the ICS entire phone encryption does not work and, according to some information I have gathered around the web, it may be due to the fact that the internal sd partition is not ext4 which seems to be required.
It may be due to the fact that the kernel does not support ext4. If this was the case, I would be very pleased to activate the option, recompile it and share the result with other people at xda. I have done it for two types of Samsung Galaxy phones.
In this case, the two problems I would be faced with are:
1) Getting the kernel sources. For Samsung it is quite easy. For Lenovo, I am not able to find them (I can't read Chinese).
2) The process to package the new compiled kernel to a zip, compatible with cwm.
Anyway, thanks for your help and to share your knowledge.
Sheers,
Laurent
Click to expand...
Click to collapse
cybermaus said:
well, not sure about encryption, but I can *assure* you that the phone supports ext4, because in fact the root; system; cache; secro and data partitions are all in ext4 . I know that quite certain, because to unpack/repack, I need to recreate an ext4 loop device.
Internal SD is indeed FAT partition. But it is normal for SD to be FAT
Click to expand...
Click to collapse
It is possible the encryption fails on the FAT of the SD card. It is an internal device, if that encryption utility tries to parse all the internal partitions, it may fail on FAT, but I am guessing here. However, then it would fail on pretty much all recent china phones, they all seem to have this internal SD card. You could try to simply format the internal SD as ext4.
I do not think it would fail on the recovery or boot sections. Those are all nicely wrapped up in the first partition of the emmc chip (emmc0p0 or something) in a proprietary filesystem, as I suspect true for all Androids. So your tool would know to exclude that the first one. However, if you want, you can get the original recovery you asked about from the original A789 ROM in my Dev-Host.
Edit: Encryption issue solved, see post#9 below
I already managed to build a multilang framework-res.apk for the A789 ROM. But now there are all those apps that need to be made multilang also - settings.apk and more... a lot of work.
Is it possible to take a P700 ROM with A750 kernel and flash it to the A750? Or a P700i ROM and A789 kernel for the A789? They seem to be almost identical.
Any plans to integrate the long press home button function in A750_ROW_S114_cybermaus_ICS_V3.1? Would like to test this rom but this missing feature is essentail for me...and onother question: V3.1 is also for A789, right? Same problem with long press home feature?
@oz42
Well, I am a little disappointed about that question. Putting the P700_ROW on the A750 is *exactly* what my V3 series is. Works wonderful. It's the reason I have been updating this thread for the last two weeks. Problem is that the only extra language is Vietnamese. You may want to re-read posts #2 and #585 in the A750 thread.
I suspect the same is true for P700i and A789, but I did not find a P700i_ROW rom yet. I did find a S880_ROW, and when I have time (later this weekend) I will check if that has proper multilanguage (edit: No. It adds ru, vi, id to en and zh. Not quite what I had hoped for)
@metzner
Yes. When I know how. But I do not have a clue at this moment. I am very pleased about the V3.1, but the missing long press is annoying me at times.
No, V3.1 is not for A789 (yet). They have different partitions, different schreen driver. YOU CANNOT flash a A750 on A789 (or any MT6575 on MT7577) without 'porting' the ROM. I do have a Frankenstein ROM, using p700_ROW with kernel/partition/modules/baseband from A789. But it was not tried out yet.
A789: Encryption problem
I have installed aLogcat to determine what could block the encryption service on the different ROMS I have tested on my A789. The interesting part revealed to be:
E/Cryptfs ( 87): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
Googling for this problem, it appears that there is a strong probability that the culprit is CWMR that I have installed almost right after getting my phone. See: http://forum.xda-developers.com/showthread.php?t=1792101 or http://rootzwiki.com/topic/25652-fixing-galaxy-tab-2-encryption/.
So if somebody has a package that can be safely used with mt6575-flashing tools, to recover the stock recovery or, much better, to install a "clean" version of CWMR, I would be glad to test it and see if it is actually the origin of the encryption problem.
Edit:
@Cybermaus: I have just noticed that you have already addressed part of this message. I have already tried to format the internal sd as ext4 with Minitool partition Wizard on Windows. This fails also. Moreover, the system reports a failure on this partition and ask to reformat it as vfat. I will try by putting back the original recovery from your 4shared. Thanks a lot.
@lolo250612
If I read that post you found, the problem is not so much CWMR or CWMRT itself, but the fact it wipes and formats /data completely, without leaving 16KB of unused space at the end of the partition.
That means replacing it with factory recovery will not help, unless if you then also wipe using that factory recovery, and that factory recovery does leave 16KB. You could also try wiping it from the settings menu.
After you have tried the factory , let me know. I think I can make an empty /data for you that is 16KB shorter than the partition, but you would have to apply it using the flash-utility method.
Edit: checking, I found that the userdata.img that is inside the original S228 factory flash ROM is already 1024K short of 768M. So 767M. No need to build one with only 16K short, just use the one you already have.
Hi cybermaus
Thanks for your contribution. Please help me if you've free time.
Does this custom ROM support traditional Chinese character?? I'm sure Chinese support would include simplified Chinese.....
@loimlo
The A750 V1 and A789 V2has two forms of Chinese, which I cannot read, but I suspect are traditional and simplified. The A750 V3 has one form of Chinese, which I still cannot read, so I am not sure which of the two, but here is a screenshot of it, let me know which it is.
Amadis223 said:
Hi, I wrote with yuweng on this subject. And it is very strange. He says, that mt6575 has only ext4 filesystem, but I,am sure,that I have mt6575 and yaffs filesystem. What do you think ?
Click to expand...
Click to collapse
Well, all the MT6575 and MT6577 based ROM's that I have dissected have ext4. This is probably because mediatek provides ext4 in their development kit. So yeah, I think all mt6575 are on ext4, and not yaffs. I think maybe the mt6573 has yaffs.
cybermaus said:
@lolo250612
If I read that post you found, the problem is not so much CWMR or CWMRT itself, but the fact it wipes and formats /data completely, without leaving 16KB of unused space at the end of the partition.
Click to expand...
Click to collapse
I agree with you.
Edit: checking, I found that the userdata.img that is inside the original S228 factory flash ROM is already 1024K short of 768M. So 767M. No need to build one with only 16K short, just use the one you already have.
Click to expand...
Click to collapse
I have flashed userdata.img. That WORKS :victory:. The phone reboots and then encryption starts. Done in less than 5 minutes. Great. Now, just have to tried one of the utility around that allows to have an encryption password different from the lock one. Many thanks for your help :good:.
hi there,
I just got a Lenovo A789 and i just installed A789_S228_cybermaus_V2.1 and it works perfecly...
i'm new to android and i can't get cellular data to work ( i have reason to believe that it worked in original ETOTALK rom, but im not sure ).
1) i do have a data plan
2) cellular data / mobile data is turned on
3) 3G card with cellular data plan is in slot 1
wrong basebands or apn settings (Portugal, Vodafone) ? ( i can see them in mobileuncletools but i cant change them )
help?
note: i cant follow most of android tips that i googled because some of the menus to edit APN settings do not exist on this rom :\
@spinal2k
Well, the simply solution would be to try and apply the A750 V1.4 as listed in post#2. It only applies location fix and new APN list, so its safe on the A789, even if it was originally for A750.
Second option would be to Google for the keyword APN together with your provider and country names.
Last option is to tell us the mcc/mnc that mobile uncle found, as well as your current APN settings, and maybe we can figure it out.
Edit: you can change APN in Settings->Wireless->More->MobileNetworks->AccessPointNames
cybermaus said:
Last option is to tell us the mcc/mnc that mobile uncle found, as well as your current APN settings, and maybe we can figure it out.
Edit: you can change APN in Settings->Wireless->More->MobileNetworks->AccessPointNames
Click to expand...
Click to collapse
ok, thanks for the tip... how can i see mmc/mnc on mobileuncle tools?
According to that wikipedia page, my MMC/MNC is 268/01 and that it uses GSM 900 / GSM 1800 / UMTS 2100.... On mobile uncle engineer mode i can see that on the 1st sim card UMTS 2100 doesn't exist ( only UMTS 2000 )... :\
acoording to the "you can change APN in..." i can't changed them, just see them... they look fine to me, they're not wrong...
:\
@spinal2k
Don't tell me the ones from that Wiki page, but the ones you find in the APN settings. And then also the "market name" of the service you have. You cannot change, but you can add a new APN, and then select that to use.
But simply applying the V1.3 may be easier, it has the APN list maintained by Cyanogenmod, and will probably solve it anyway.
cybermaus said:
@spinal2k
Don't tell me the ones from that Wiki page, but the ones you find in the APN settings. And then also the "market name" of the service you have. You cannot change, but you can add a new APN, and then select that to use.
But simply applying the V1.3 may be easier, it has the APN list maintained by Cyanogenmod, and will probably solve it anyway.
Click to expand...
Click to collapse
oh, i couldn't see that i could add new.... Now i added an optional apn ( even though the one listed was on official carriers page ) ... now its working...
Thank you for the tips... keep them updates coming
note: i did update with A750 v1.3 and i saw no changed in apn list...
A750 V3.1 battery life
I have been using the cybermaus V1.3 ICS for ages, and it works really well. Recently tried the V3.1 ICS.
Also seems to work really well as well, and a definite plus is the 3G signal strength - I see a definite improvement.
There is a dealbreaker problem for me, though - the battery life is noticeably worse than the excellent life on the V1.3 rom. I'm a noob - tried clearing user cache/dalvik, but not reset (I want to keep my apps/data).
Any suggestions before I go back to V1.3 - thanks.
zapzog said:
Any suggestions before I go back to V1.3 - thanks.
Click to expand...
Click to collapse
Well, a request more than a suggestion: your battery is now a few months old, so slightly less good then when new, but you got used to it. But now, due to the flashing of a new ROM, you are playing on it more, and it is in your attention very much.
I cannot properly test myself, I have to tether it daily for data access. So please try to get a proper test of it:
Stay with V3.1 a few bit longer, at least 2 battery cycles extra. (you can barely have had one) so you get a better baseline. Charge the same method as before (I find that charger works better than PC-USB) After two more cycles, when you have a proper idea on the life, go back, and get a renewed baseline on V1.3 also. And then report your results
Related
I have been working on some boot/recovery ROM rebuilds for the Garmin/Asus Garminfone A50 (T-Mobile), as well as the scripts and instructions... I'm not sure where to host them.
I personally don't want to host them myself, and was wondering if there is a repository of sorts.
At the moment, I have the following:
* The tools necessary (dump_image & flash_image) to dump the firmware from the phone
* The scripts necessary to unpack/repack the boot/recovery ROM's (modified to support the Garminfone's different address layout). Linux based.
* Pre-built boot and recovery images that give permanent root and mount the system/data partitions as r/w by default.
* Instructions on how to do it yourself, complete with some tech info on the layut of the Garminfone boot/recovery images and how to verify before you flash it that it built properly.
* Instructions on how to flash the phone without risking bricking it, since there is no hardware key combo to get into recovery and a fastboot that's not fully implemented. The technique goes like:
- Verify with a hex editor that the proper addresses are in the header
- Flash the new boot image to recovery
- Reboot into recovery to make sure it boots the new boot image properly
- Flash the rooted recovery image to the recovery partition
- Reboot into recovery once more and verify that works
- Flash the tested boot image to the boot partition
- Reboot normally and have fun
That method works fairly well, and unless you target the wrong partition, and gives you a 99.9% success rate
I'm going to post what I can on the Wiki (as far as instructions go), but it would be nice if I had a place to put the tool set as well.
I'd rather not use one of the temporary sites like Mediafire or what not, since files on those sites have a tendency to disappear.
Please no PM's on having me send them the files directly. I don't have a heck of a lot of spare time and don't want to get into the habit of sending these out manually.
If you're against the typical file hosts and the files aren't too big you could try using dropbox or sugarsync and sharing the links.
Can I ask you a question? I have a Kyocera ZIO M6000 and have the openzio clockworkmod 2.5.1.1 port that only works with "fastboot boot openzio-recovery" and we have tried flashing to our recovery partition with no success. What will it take to break the tether and reboot recovery locally without fastboot?
Sent from my Zio using XDA App
merwin said:
I have been working on some boot/recovery ROM rebuilds for the Garmin/Asus Garminfone A50 (T-Mobile), as well as the scripts and instructions... I'm not sure where to host them.
I personally don't want to host them myself, and was wondering if there is a repository of sorts.
At the moment, I have the following:
* The tools necessary (dump_image & flash_image) to dump the firmware from the phone
* The scripts necessary to unpack/repack the boot/recovery ROM's (modified to support the Garminfone's different address layout). Linux based.
* Pre-built boot and recovery images that give permanent root and mount the system/data partitions as r/w by default.
* Instructions on how to do it yourself, complete with some tech info on the layut of the Garminfone boot/recovery images and how to verify before you flash it that it built properly.
* Instructions on how to flash the phone without risking bricking it, since there is no hardware key combo to get into recovery and a fastboot that's not fully implemented. The technique goes like:
- Verify with a hex editor that the proper addresses are in the header
- Flash the new boot image to recovery
- Reboot into recovery to make sure it boots the new boot image properly
- Flash the rooted recovery image to the recovery partition
- Reboot into recovery once more and verify that works
- Flash the tested boot image to the boot partition
- Reboot normally and have fun
That method works fairly well, and unless you target the wrong partition, and gives you a 99.9% success rate
I'm going to post what I can on the Wiki (as far as instructions go), but it would be nice if I had a place to put the tool set as well.
I'd rather not use one of the temporary sites like Mediafire or what not, since files on those sites have a tendency to disappear.
Please no PM's on having me send them the files directly. I don't have a heck of a lot of spare time and don't want to get into the habit of sending these out manually.
Click to expand...
Click to collapse
I would also suggest dropbox or even id host them off my computer via ftp
Can your method work with Garminasus A10?
Merwin you still working on this?
Yeah, I am working on it still. I am still looking for a better place than dropbox or hosting off of someone's home PC...
As for the A10, if you can get me a dump of the boot and recovery images I can make one for that too... you will want to preferably use the dump_image utility to get the image and the flash_image utility to flash it.
I can probably attach those to a post with dump instructions. They're tiny.
Basically, you root your phone, copy the files to a certain location, type a couple commands to fix permissions on the executables, then run a command to dump the image.
Flashing back requires clearing the boot or recovery partition with a command and then using the flash_image command to flash it.
My method tests the new boot image first by flashing it to recovery first and rebooting into recovery to make sure the new image works. Then flash the modified recovery image to the recovery and make sure it is rooted (so you can get things up again if something does go wrong). Then you flash the new tested boot image to boot. If, for some reason, that fails, it should reboot automatically into recovery after a few boot failures. Never had to test that, since I pre-test all images I make.
hi merwin, we are a fans group of GA a10 and we trust a lot in your work! if you need any kind of help contact me! probably you are the first in the world who can flash a GA phone
Merwin, Im not completely sure which type of place your looking for if its not either ftp or online file sharing
Rapidshare
2shared
Filefront
4shared
Hi merwin,
I found this page, is that similar to your method? Hope you guys can find out something.
http://mygarminfone.blogspot.com/
afoster1003 said:
Merwin, Im not completely sure which type of place your looking for if its not either ftp or online file sharing
Rapidshare
2shared
Filefront
4shared
Click to expand...
Click to collapse
You forget one widely used protocol. Good old http on a standard web server.
Those other sites annoy me greatly, between the amount of ads, having to wait to download and daily limits, and the fact that they are temporary unless I pay. I am against them on principle.
I figure if there is enough interest, someone will step up to host them, otherwise I will just provide scripts, instructions, and technical info for people to do it themselves.
slumpz said:
Hi merwin,
I found this page, is that similar to your method? Hope you guys can find out something.
http://mygarminfone.blogspot.com/
Click to expand...
Click to collapse
You are my hero That blog has the missing pieces I need to keep going.
A couple of days ago I found some info on how to decompile the .update files which gives us the recovery image and system partition from any other phone that uses a similar format, like the Asus A10... providing a whole host of opportunities for the Asus phones that are still being maintained.
For instance, I grabbed the files from the Chinese A50 that has newer firmware.
With the info from the blog, I may be able to at least compile and integrate the newer kernel and wifi firmware (which is stored on the phone and loaded into memory at boot). The Chinese version does have newer wifi module firmware in it... whether it is compatible or not is another story.
On another note, has anyone successfully downloaded the open sources kernels from Asus? I have tried every method on their site and all but a couple of the kernel versions in the zip are corrupt. One from march extracts fine, so I may use that as a base to start with.
merwin said:
You are my hero That blog has the missing pieces I need to keep going.
A couple of days ago I found some info on how to decompile the .update files which gives us the recovery image and system partition from any other phone that uses a similar format, like the Asus A10... providing a whole host of opportunities for the Asus phones that are still being maintained.
For instance, I grabbed the files from the Chinese A50 that has newer firmware.
With the info from the blog, I may be able to at least compile and integrate the newer kernel and wifi firmware (which is stored on the phone and loaded into memory at boot). The Chinese version does have newer wifi module firmware in it... whether it is compatible or not is another story.
On another note, has anyone successfully downloaded the open sources kernels from Asus? I have tried every method on their site and all but a couple of the kernel versions in the zip are corrupt. One from march extracts fine, so I may use that as a base to start with.
Click to expand...
Click to collapse
I have, magically I might add. I downloaded the source for v.5.0.70 and managed to get it compiled. The resulting files can be found on on my blog, the one Slumpz posted(I can't post links yet, lol.)
The only problem is, I don't have much experience with anything linux. But, If you have any questions Merwin, email me, [email protected].
Here's a little how to, just check my blog, or google: How To: Build Garmin-Asus Kernel from Source.
am willing to giv a subdomain/storage ftp access on this domain for the good of the community if it helps any
Domain darkjester.net
Disk Usage 5.4 / 1500.0 MB
Bandwidth 100000 MB (100GB)
Home Root /home/a2931495
Apache ver. 2.2.13 (Unix)
PHP version 5.2.*
MySQL ver. 5.0.81-community
Activated On 2011-05-15 14:42
Status Active
Hello guys, are you still working on this.
I found out that A10 has a new firmware posted, which is versioned 5.2.7 instead of 5.0.x like the others. I wonder if there's any method to test this firmware on foreign A10 (non Chinese firmware)?
So, got an HTC Sensation 4G... meaning not much more work on the Garminfone for me.
Still trying to find time to compile everything that I have done into some semi-coherent document with the unlocked boot and recovery images. I still have the Garmin, so if someone manages a huge breakthrough then I may pick it up again. Really didn't want to get rid of the phone but there just isn't enough community development going on to make it worthwhile.
By the way, the Garminfone GPS blows every other phone away. The Sensation 4G is crap in comparison.
Please excuse asking questions as a first post, but I'm at the stage where I'm stumped and a search isn't helping.
Mlais MX28 fresh from MM pre-rooted. Managed to get the ROM backed up and CWM installed with Rua1's excellent MTK Droid Root & Tools. However, removing the Chinese useless (for me - no offence intended) apks proved not to be happening from the one-click button in that excellent piece of software. No bother, thought I, I'll just use adb and remove the relevant apks manually from /system/app. Famous last words.
Here's where things get really odd. I can mount root fine using the usual procedure but mount -o rw,remount /[email protected] /system works once and once only. Even stranger is that the first time gets you a rw mounted filesystem for about 10 seconds, at which point it gets remounted ro and no amount of faff will get it back to rw without a full power off and restart. All it does is spits out
Code:
mount: Read-only file system
Any ideas, please? I suspect there's some write protection going on but I haven't the first idea where to look.
Edit: Having done a little more searching on this issue, it seems there's a few Acers with the same behaviour, caused by a compiled-in kernel option. Looks like it may well be "wait for a custom ROM" is the answer. Not sure if rolling our own is possible unless anyone knows where to get the Mediatek sources for this device from?
Anyway, :good: to all those who have viewed my question. It's appreciated.
Edit 2: There's an S4UI ROM on needrom<dot>com that is rumoured to have solved this issue. Note that if you have installed CWM using the "magic" MTK Droid Root & Tools method, chances are you can't mount /system rw using ADB in CWM either - I suspect they share the same kernel. I haven't tried the S4UI ROM myself as the recovery needed to install it seems to be in Chinese. Possible solution for anyone with a grasp of that language and script but that someone isn't me
[Q] Mlais MX28 Recovery in Chinese Any help with translation
Hello, bud Any help yet also gut stuck in this.
I'm afraid not at the moment. The S4UI ROM on needrom does indeed enable /system rw but the WiFi and Bluetooth will not activate. Replacing mtk_stp_wmt.ko in /system/lib/modules/ with the version from the stock ROM that should fix this issue, doesn't fix this issue. It's a shame as the S4UI ROM is rather pleasant to use and if I could get that fully operational I expect I would be quite happy with this device. Oddly, the stock ROM came back with a different MAC for the WiFi. As I restored from a backup created with MTKDR&T, this is a little perplexing.
I'll update if I find any more clues.
{Possible solution/nasty hack]
Here's a way to get full /system access on the stock ROM. It requires
Clockwork Mod recovery
ADB
Courage
Install/create Clockwork Mod with MTKDR&T. Now boot into recovery by holding Vol+ and power until the boot selection screen appears and then select recovery with Vol+ and press Vol- to accept.
Do not mount /system in CWM.
On your ADB equipped computer, start
Code:
adb shell
Now issue the following at the root shell prompt:
Code:
tune2fs -e continue /dev/block/mmcblk0p5
Reboot the system and enjoy the power of full root.
This may well be a nasty hack. I was convinced the issue was a protected kernel module but it seems the ext4fs image of the system block is corrupt in some way and the default error action is to mount -o ro. We're disabling that default action and letting the mount remain unchanged.
As always with these things, proceed at your own risk. If you break it, you have the privilege of keeping both bits.
Good way around mate, but risky as no CWM yet installed, seem's the mobile gut some bug problem, should expect an official update rom soon enough, Root method you used for this? i intend flashing Clockwork Mod can seem to understand fully as i'm new to android development and customizing, again problem with battery do you get a full day (few moment on screen) light usage? Feel its no actual 25000mah on board.
codedmax said:
Good way around mate, but risky as no CWM yet installed, seem's the mobile gut some bug problem, should expect an official update rom soon enough, Root method you used for this? i intend flashing Clockwork Mod can seem to understand fully as i'm new to android development and customizing, again problem with battery do you get a full day (few moment on screen) light usage? Feel its no actual 25000mah on board.
Click to expand...
Click to collapse
It appears there's an fsck implementation in the shell of CWM as well.
Code:
e2fsck -pfv /dev/block/mmcblk0p5
That should fix most of the errors in the filesystem.
The device came with su and SuperSU installed but it was fairly useless without /system access.
CWM can be easily installed using MTK Droid Root & Tools to extract the boot image, auto-patch, build CWM and install the lot. It really is a slick piece of software.
As for the battery, an even bigger issue is the supplied charger which is puny. Of course, looking at the battery and then looking at a proper, honest-to-goodness 2.2Ah Panasonic 18650 cylindrical cell you have to wonder if 2.5Ah isn't awfully optimistic.
Chron0s said:
It appears there's an fsck implementation in the shell of CWM as well.
Code:
e2fsck -pfv /dev/block/mmcblk0p5
That should fix most of the errors in the filesystem.
The device came with su and SuperSU installed but it was fairly useless without /system access.
CWM can be easily installed using MTK Droid Root & Tools to extract the boot image, auto-patch, build CWM and install the lot. It really is a slick piece of software.
As for the battery, an even bigger issue is the supplied charger which is puny. Of course, looking at the battery and then looking at a proper, honest-to-goodness 2.2Ah Panasonic 18650 cylindrical cell you have to wonder if 2.5Ah isn't awfully optimistic.
Click to expand...
Click to collapse
Very Well concerned,
once again good job, but how do i go about implementing this,
would you be kind enough to put in some more details on the file system code and CWM flashing with MTK Droid root & Tool did you manage to get a translation on the chinese langauage recovery problem,
(a tutorial is just fine) Thanks alot bud.
Okay, give me a little time to set it all up for screenshots as I don't generally use Windows unless I have to. It's all fairly straightforward. The CWM installation is four clicks and some waiting and repairing the /system block is a couple of commands.
Oscarblue48 has a tutorial on installing CWM on Mediatek devices here or here if your MX28 isn't rooted which is the procedure I followed. Then it's just a case of booting into CWM, connecting your device to USB and using adb's shell to fsck the filesystem on that block.
really nice, okay as you say,
i would look forward to it (some screen shots aid), in the main time with full study & concentration on the CWM tutorial you gave, quite interesting if you ask me.
#back to studying, looking forward to a bug free final optimization of the Mlais MX28 as its a great buy for such a price.
codedmax said:
really nice, okay as you say,
i would look forward to it (some screen shots aid), in the main time with full study & concentration on the CWM tutorial you gave, quite interesting if you ask me.
#back to studying, looking forward to a bug free final optimization of the Mlais MX28 as its a great buy for such a price.
Click to expand...
Click to collapse
Sorry for the delay, I ran into a few issues and had to work out what was going on. Basically the e2fsck in CWM cannot write back to the block device so is useless. I extracted the system.ext4.img, added it as a file backed memory disk on my main computer and ran an e2fsck from there, which found and fixed the errors in the FS image. Writing that back after changing a few MD5sums in the file MTKDR&T creates allowed me to flash it back.
However it makes absolutely no difference to the mount behaviour. It still drops back to ro without the tune2fs -e continue set so that is, barring someone else coming up with a more elegant fix, the workaround. In a nutshell, follow the guide for either root or CWM recovery installation that others have posted linked above (no point wasting board space on repetition) and then simply follow my instructions for setting the error behaviour on the mmcblk0p5 slice and you should be good to go.
It's still an awful hack IMHO but, since there's nothing else so far that works, it's the uncomplicated way to get full root. Most of us will install CWM anyway, so it's no big chore just to boot into recovery and type one command "tune2fs -e continue /dev/block/mmcblk0p5" at the ADB shell.
Chron0s said:
Sorry for the delay, I ran into a few issues and had to work out what was going on. Basically the e2fsck in CWM cannot write back to the block device so is useless. I extracted the system.ext4.img, added it as a file backed memory disk on my main computer and ran an e2fsck from there, which found and fixed the errors in the FS image. Writing that back after changing a few MD5sums in the file MTKDR&T creates allowed me to flash it back.
However it makes absolutely no difference to the mount behaviour. It still drops back to ro without the tune2fs -e continue set so that is, barring someone else coming up with a more elegant fix, the workaround. In a nutshell, follow the guide for either root or CWM recovery installation that others have posted linked above (no point wasting board space on repetition) and then simply follow my instructions for setting the error behaviour on the mmcblk0p5 slice and you should be good to go.
It's still an awful hack IMHO but, since there's nothing else so far that works, it's the uncomplicated way to get full root. Most of us will install CWM anyway, so it's no big chore just to boot into recovery and type one command "tune2fs -e continue /dev/block/mmcblk0p5" at the ADB shell.
Click to expand...
Click to collapse
Greetings bud, gut CWM installed, all thanks to you (indeed greatful), have you been lucky with any custom rom as of now that works efficently on your device?
I seem to find a few bug here and there on the manufacturer stock, puny wifi & gps lock in, slight screen maulfuctions a little times.
As with most mtk gps can not finding a lock in hows it with your device.
codedmax said:
Greetings bud, gut CWM installed, all thanks to you (indeed greatful), have you been lucky with any custom rom as of now that works efficently on your device?
Click to expand...
Click to collapse
None of the custom ROMs on needrom work correctly which is a shame. The stock ROM's UI is awful.
codedmax said:
I seem to find a few bug here and there on the manufacturer stock, puny wifi & gps lock in, slight screen maulfuctions a little times. As with most mtk gps can not finding a lock in hows it with your device.
Click to expand...
Click to collapse
Now you have root you can use FasterGPS from FDroid to intialise the gps.conf file with appropriate settings for your location. My GPS is rock solid now, even in a moving vehicle. Not had any screen malfunctions. What version is your stock ROM? Mine's the 20140221 update.
Chron0s said:
None of the custom ROMs on needrom work correctly which is a shame. The stock ROM's UI is awful.
Now you have root you can use FasterGPS from FDroid to intialise the gps.conf file with appropriate settings for your location. My GPS is rock solid now, even in a moving vehicle. Not had any screen malfunctions. What version is your stock ROM? Mine's the 20140221 update.
Click to expand...
Click to collapse
Hello great bud,
Sorry for late reply, been up with alot on my plate from work lately, gps has been improved upon using that wonderful app "FasterGPS" now able lock in under a split couple of min not as before were it take like forever *Nice*
gut the same stock version "20140221" gusse its down to my own unit with the screen ish
Did a little searching around found a recent update from a online retailer outlet via their forum "merimobiles"
forum.merimobilesdotcom.previewdnsdotcom/showthread.php?465-Unified-thread -for-Mlais-MX28-stock-ROM-updates
Hope im not infringing on any xda TOS as i just seek some help.
Thanks
Please i need help, i have a mlais mx28 buy in buyincoins, with the refer gordete200, it´s all ok.
i´m very happy with the mlais mx28, but i used a 8 gigas sd card, it´s all ok.
My problem: i have install with flashtools the new rom stock update : mx28_0312_N2.rar from the official mlais mx28 web
When i have install this ultimate ( update ) ROM, it´s was with reebots, and the wifi and blutooth crash 0_0 !!! what happend?
I back to the Rom stock : 0115 but the sd partitions was changed : 1 gb for apps, and 1.75 gb for internal memory, it´s very strange, before install the Update, i had 2,3 gb for apps and 256 gb for internal memory...
I´m very worry, the actual problem is the sd card:
With 8 gb sd card class 10, it´s all ok, all correct, but when i put the 16 gb sd card class 10, it´s don´t mount sd correctly always.
I´m very crazy for all...
codedmax said:
Hello great bud,
Sorry for late reply, been up with alot on my plate from work lately, gps has been improved upon using that wonderful app "FasterGPS" now able lock in under a split couple of min not as before were it take like forever *Nice*
Click to expand...
Click to collapse
Good stuff. Once you have the gps.conf set up, try using Mobileuncle Tools to pull in the EPO (extended prediction orbit, basically a nice big list of keplers for the satellites so it knows which to expect to be in view at a given time without having to scan the sky for what's actually there) data which should stabilise the GPS even further.
codedmax said:
gut the same stock version "20140221" gusse its down to my own unit with the screen ish
Did a little searching around found a recent update from a online retailer outlet via their forum "merimobiles"
forum.merimobilesdotcom.previewdnsdotcom/showthread.php?465-Unified-thread -for-Mlais-MX28-stock-ROM-updates
Hope im not infringing on any xda TOS as i just seek some help.
Thanks
Click to expand...
Click to collapse
I wonder if it's the bodged Trebuchet they're using? It's a bit of a disaster as they've taken the CM launcher, bodged bits of MIUI into it and given the whole thing a "that'll do" look and feel. I replaced it with the real Trebuchet after a thorough decrapify, along with the AOSP stock keyboard. There's a "modified" apk of Trebuchet (all the dev did was lower the base API level so it would install on 4.1) floating about on the 'net somewhere. The various KitKat-alikes work fairly well but I wanted something open source that I could slam into /system/app without worrying.
It has taken a lot of faff to get to this stage but I now have a very usable and fast device for not a great deal of outlay.
gordo100 said:
Please i need help, i have a mlais mx28 buy in buyincoins, with the refer gordete200, it´s all ok.
i´m very happy with the mlais mx28, but i used a 8 gigas sd card, it´s all ok.
My problem: i have install with flashtools the new rom stock update : mx28_0312_N2.rar from the official mlais mx28 web
When i have install this ultimate ( update ) ROM, it´s was with reebots, and the wifi and blutooth crash 0_0 !!! what happend?
I back to the Rom stock : 0115 but the sd partitions was changed : 1 gb for apps, and 1.75 gb for internal memory, it´s very strange, before install the Update, i had 2,3 gb for apps and 256 gb for internal memory...
I´m very worry, the actual problem is the sd card:
With 8 gb sd card class 10, it´s all ok, all correct, but when i put the 16 gb sd card class 10, it´s don´t mount sd correctly always.
I´m very crazy for all...
Click to expand...
Click to collapse
Do you have a backup of the original ROM and scatter (partition layout) file? You really should (read: MUST) back up these devices before flashing new firmware as there's often bits missing, as you found with the WiFi and Bluetooth issue. MTK Droid Root & Tools will create a useful backup of the partition layout and contents for you without too much difficulty.
Please do not write to the preloader partition with the SP flash tool. Once the preloader is corrupt, your device is a brick which only JTAG will recover. I seriously doubt anyone has a JTAG solution for this device right now. There is no need to rewrite the preloader at all in any case so simply deselect the preloader block in SP Flash tool before downloading.
As for the SD cards, you need to make sure your card is formatted FAT, not NTFS, and the card must be partitioned correctly, i.e. the FAT partition must be the first primary. The MX28 will accept a card of up to 32GB if I recall correctly, which is the limit of SD-HC. Clockwork Mod can format your card for you.
Chron0s said:
Do you have a backup of the original ROM and scatter (partition layout) file? You really should (read: MUST) back up these devices before flashing new firmware as there's often bits missing, as you found with the WiFi and Bluetooth issue. MTK Droid Root & Tools will create a useful backup of the partition layout and contents for you without too much difficulty.
Please do not write to the preloader partition with the SP flash tool. Once the preloader is corrupt, your device is a brick which only JTAG will recover. I seriously doubt anyone has a JTAG solution for this device right now. There is no need to rewrite the preloader at all in any case so simply deselect the preloader block in SP Flash tool before downloading.
As for the SD cards, you need to make sure your card is formatted FAT, not NTFS, and the card must be partitioned correctly, i.e. the FAT partition must be the first primary. The MX28 will accept a card of up to 32GB if I recall correctly, which is the limit of SD-HC. Clockwork Mod can format your card for you.
Click to expand...
Click to collapse
Many thanks for your help. I have a back up of my mlais, i have a back up with mtk droid and tools 2.5.3 ( new version ), but when i put it on the flash tools, the cache and user is missing, and it´s imposible to download it. and then i put a recovery CWM on the mlais with droid and tools ( very easy ), and use a nandroid back up, it´s no problem, but the internal sd partition is always changed : 1 gb for apps and 1.75 for sd internal, i´m very sad because i would like back to the 2,3 gb for apps ( original partition )
Yes... always fat32 sd cards of course, but i have problems with the sd up to 8 gb, the mlais freeze, or sd desmount ( it´s imposible sometimes write in sd external ) i don´t find the problem with this... i have the rom stock : 115.
Other problem, i would like to up the ultimate ROM stock 221. but the wifi and bluetooth crash, and reboot the phone sometimes ( terrible...) , what can i do ? your solution is don´t stick the PRELOADER on the Flashtool when i upload the firmware ? it´s correct? ( i think that if don´t mark the preloader it´s imposible flash... ?¿ )
Many thanks for your help !
gordo100 said:
Other problem, i would like to up the ultimate ROM stock 221. but the wifi and bluetooth crash, and reboot the phone sometimes ( terrible...) , what can i do ? your solution is don´t stick the PRELOADER on the Flashtool when i upload the firmware ? it´s correct? ( i think that if don´t mark the preloader it´s imposible flash... ?¿ )
Click to expand...
Click to collapse
No, what I'm saying is we don't yet know why the WLAN and Bluetooth stop working when a different ROM from the one flashed at the factory is installed. There is clearly some mechanism at work here that is blocking those two devices after an update and it's not the usual shared objects as it is on other devices. It also doesn't seem to be NVRAM related as the MAC and BDaddr remain once the old firmware is re-flashed.
This same problem occurs with all the custom ROMs on needrom.
The reason I say do not needlessly flash the preloader is the danger of a full brick from which you cannot recover. The preloader code very rarely changes - its only purpose is to provide an interface to SP flash tools or boot; think "BIOS" in PC terms - so it is a pointless risk. You most certainly can flash the other blocks with the preloader block deselected.
The bottom line right now is stick with the factory ROM, install CWM, apply the system mount fix and use Xposed and suchlike to customise until we come up with something a little more sensible or at least find out why the WLAN and Bluetooth stop working.
Given that the Wiko Darkmoon is based on the same SoC and has full sources available <EDIT: It isn't. It's just the kernel as usual.>, it may be prudent to wait until someone with more clue than I has a look at what makes these things tick.
Chron0s said:
No, what I'm saying is we don't yet know why the WLAN and Bluetooth stop working when a different ROM from the one flashed at the factory is installed. There is clearly some mechanism at work here that is blocking those two devices after an update and it's not the usual shared objects as it is on other devices. It also doesn't seem to be NVRAM related as the MAC and BDaddr remain once the old firmware is re-flashed.
This same problem occurs with all the custom ROMs on needrom.
The reason I say do not needlessly flash the preloader is the danger of a full brick from which you cannot recover. The preloader code very rarely changes - its only purpose is to provide an interface to SP flash tools or boot; think "BIOS" in PC terms - so it is a pointless risk. You most certainly can flash the other blocks with the preloader block deselected.
The bottom line right now is stick with the factory ROM, install CWM, apply the system mount fix and use Xposed and suchlike to customise until we come up with something a little more sensible or at least find out why the WLAN and Bluetooth stop working.
Given that the Wiko Darkmoon is based on the same SoC and has full sources available <EDIT: It isn't. It's just the kernel as usual.>, it may be prudent to wait until someone with more clue than I has a look at what makes these things tick.
Click to expand...
Click to collapse
Many thanks Chronos!, The problem is also with the official ROMS on mlais.com/mlaismx28 i don´t understand it...
Please i need help to back restore the partitions of my sd internal ( ROM ), i would like back to 2,3 gb for apps, actually i have only 0,98 gb and 1,75 gb internal store.
I think that the solution is back up for flash tools and reflash with the rom stock ( the back up of mlais mx28 of my friend, he have other new mx28 )
But my BIG problem with the flash with flash tools is the USER DATA and CACHE is always empty, and then it´s imposible to reflash it it´s always and error : Rom changed PTM ...
Please, what can i do for have USER DATA and CACHE with mtk droid and tools 2.5.3 versión?? ( in this version to click User data and Cache with to do the back it´s imposible, this option is missing in 2.5.3. version )
http://dl.xda-developers.com/attachdl/b2f11c741aab592a8f66616d932af983/533c2dcc/2/6/6/4/5/2/2/Sin_t_tulo.jpg
[ROM] Official Update
Hello guys, there's a new rom update for the mx28
Official Mlais MX28 version: Mlais_MX28_20140312
www.needrom.com/mobile/mlais-mx28-2/
Try it out seems, it works perfect.
Cheers!!
Hi all,
After spending many hours trawling the internet, and especially this forum I still am having problems getting ANY custom rom I've tried booting on this phone
I know it's old, but it's just a phone I had lying around and want to use it as a small tablet for my 6yo daughter.
I can flash any "stock" rom I've found with odin, but when flashing using an install from an SD card through CWM, it just hangs on the Samsung bootscreen.
CWM installs as the default recovery console, so something is going on the phone, but it won't boot to android.
Oh I'm also using a 5830I rom, but my research has shown this is basically the same phone?
I've used CM7 and tried lots of other custom roms with the same outcome - please can anyone help!?
My daughter is dying to use her new games machine, but the stock rom is sooooo laggy and slow it's no good at all!
Thanks in advance.
@macsbig, "About device" information from settings of your device please < home+power button for screenshots > or kindly state the full details here.
Your original CSC/PDA/MODEM parts of your device <Dial *#1234# >
Your Region /Country/ carrier you are staying please.
Thanks for the reply ehsanotaku!
PDA : S5830iXXLA4
PHONE : S5830iXXLA2
CSC : S5830iOXXLA2
I'm in the uk. This is not the original rom (that got stuck in a bootlock) and the only way to get the 'phone working again was to flash with a stock rom from the internet.
The original rom was from "Three".
During my various attempts at flashing a rom I have ticked the "re-partition" box and tried both "cooperve_0623.pit" and totoro_0623.pit
I've flashed my P5110 tablet, and a Galaxy S1 for my son with no problems - odd!
@macsbig, How come you are ended up with outdated ( 2012 ) s5830i in the first place ? Any particular problems with your s5839i original firmware ( do you know your original CSC/PDA/MODEM parts ) ? Are you absolutely sure this is not re-branded version ( "About Device" info of the original phone would be nice to see though ) Did you take any Nandroid back up of all of the original partitions of your s5839i through temporary CWM zip file ( files will be stored inside your Clockworkmod directory inside the root of the SD card )
Do you still have access to Recovery stock e3 console and Download mode ?
Another important subject in need of clarification are ".pit" files ( partition table info ) and Re-partition option. Playing around with wrong .pit file such as totoro and incorrect usage of Re-partition will lead into hard bricking of your device .
Since you already did modify partition table couple of time partially without success , I would suggest the following process :
1. Download one of the newest non wipe xxx.tar.md5 s5830i firmware from here < It is free, but registration is required > Probably 2013 xxMD1 is the right one for our experiment.
2. Make your wipe flash able zip package through splitfus2 tutorial provided here, my comment @ post 9 or simply you may use European/Russian pre-made package from here , your choice though ( I would advise the first method , but the latter also will work ) .
3.Get the following files:
3.1 - Odin3.v3.07.Cooperve.exe from either places would be fine : 1 , or any sticky post in general/development section will do ( correct cooperVe .pit file will be resided inside the package )
3.2- Get the Temp-CWM 5.0.2.6 or 5.0.2.8 zip file from here or here < put the zip file inside the root of your SD card for flashing later >
3.3- Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar from post#27 , my attachment .
3.4 - SLIM_CM7.2_Cooperve #4 Rom < put it inside the root of SD card >
3.5- This kernel is also goes into Root of SD card for later usage .
3.6- EXT4 Formatter Tool , into the root of SD card again.
4- Now , if you don't have proper drivers installed inside your Windows PC , you can get then form here .
Ok, assuming you have at least access to Download mode , provided the combo keys work (pressing Vol(+) + Vol(-) + Power Keys) Go there according to manual :
-Power off your Phone.
-Get into "Download mode" by pressing Vol(+) + Vol(-) + Power Keys.
-press volume up
-Open Odin3.v3.07.Cooperve.exe
-Connect your phone to PC via USB cable.
-Make sure that your phone is detected in "ID:COM" area.
- Put your wipe PDA/CSC/MODEM/ boot loader/pit files into their proper places , Re-partition is ticked , Factory reset and reboot selected by default >> push the START !
- DO NOT disconnected nor disturb the flashing Nand process , until the process being terminated . Now you must be out of boot loop .
For completing our partition conversion and also put some cm7.2 custom Rom into the test at the same time , do the following :
- Boot into stock e3 recovery >> wipe data and flash your Temp CWM
- CWM > wipe data > wipe cache > wipe Dalvik cache
- Flash the EXT4 Formatter tool, so whole system will be converted to EXT4. (Stock filesystem is RFS).
- Flash kernel_CM7_v4.0_cooperVe .
- When the Kernel is installed, go to the advanced menu --> "reboot recovery" (this will reboot the device, thus you will be directed into your new CWM built-in, which is implanted inside Kernel ).
- Wipe data, cache and Dalvik
- Go to "mounts and storage", and make sure /system partition is mounted (will show -unmounted ; it is like ON/OFF switch)
- Main menu > "Install zip from SD Card" > choose "zip from SD card" and install the ROM, you have already got inside your SD <SLIM_CM7.2_Cooperve #4>
- Reboot
waiting for some good news ............
It's a long story, but here goes!
I had a couple of old phones we no longer use hanging around the house, so I thought it would be good to let my (young) children use them as simple games playing deivices. It doesn't matter too much if the phone is dropped and damaged etc, as I probrably wont use them for anything else as we have new phones.
Within a couple of days - and I'm not sure what happened, my daughters phone was stuck in a boot loop (samsung and "Three" logos repeatedly). Having no experiance of "unbricking" phones I immediately reached for google, and set out on my quest to sort out her phone for her (as we had lots, and lots of tears over her new toy!). The phone has no sim card in and is on wifi for installs etc.
After searching I found a rom that would load on and make the phone good again, this one: S5839iXXLK2_S5839iH3GLC2_S5839iNELK1_HOME.tar.md5
This worked ok, but was very laggy, and irritated me imensely as I was sorting games etc for her, so I decided to to instal a custom rom. After 3 roms refused to load (just stuck on the "Samaung GALAXY Ace GT-S5839i boot screen) I decided to try flashing it to 5380i firmware and Pit file - as nearly all custom roms for the ace seem to be for the 5830i variant - I wondered if this would sort my problem!
It didn't! But now it has become a challenge, and a chance to learn something of Android and how it works - as I said in my last post I have successfully flashed an I9000 with carbon and my P5110 with CM11, I learnt how to do this by what I've learnt from reaserching about this phone, so it has been a worthwhile excercise!
But back to the point. No I don't have any back-ups of the original phone, I neither had the knowlege, or know how of having or needing to do this - it's only now I'm finding my phones/tablets so facinanting!!
Yes I am now back to the stock (e3) recovery, which I can get into.
Many thanks for your help so far - I will try your ideas and repeort back!
@macsbig, Yes do that please and after resolving your initial problems , here is a confirmed list of the games compatible with your GPU/CPU of your child's legacy device . Also you can use chainfire 3d only under stock firmware/rooted phone for the games required plugin(s) and app being activate for proper almost lag free experience . You may read theses links as well for some insight : 1 , 2 .
The ext4 formatter link doesnt work my friend
macsbig said:
The ext4 formatter link doesnt work my friend
Click to expand...
Click to collapse
Just cross-linking it ( wasn't my links to begin though ^:^ )
Attached the flash able zip file to the post body .
I will try you solution(s) later. Working late today! But wow this seems quite complicated! ! Hehe.
Sent from my GT-I9300 using XDA Free mobile app
macsbig said:
I will try you solution(s) later. Working late today! But wow this seems quite complicated! ! Hehe.
Click to expand...
Click to collapse
Well , researching a new area of knowledge ( in this case customization/rooting/bricking/moding and many more technical things inside XDA) can be a bit overwhelming.I do agree with you that the sheer wealth of material means that it can be overwhelming, but more you read and spend time @ XDA, more you will get the hang of the material presented here .
Nevertheless we are here to share/help all of the possible/working solution mate. Just ask anything you can not understand very well . I will try to depict even more detailed walk-through guidelines.
Regards
Right, I now have a custom rom on the 5839i!
I didn't have too much time last night, so what I did was flashed the phone with Odin, using the bootloader and pit file you specified. I then rebooted into the stock revovery, wiped the Data, Cache and Delvic partitions, then booted into CMW 5.0.2.6 and flashed the EXT4 Formatter tool. I then installed the kernel you specified
After that I rebooted into the CMW recovery from the new kernel and followed your instructions - and Voila! It booted into the slim rom you linked me too
Just to test it wasn't a fluke, I then installed CM9, and that went on fine too - with just the normal steps.
I now have to decide after your other advice, whether I go for a stock rom, and try and get rid of the lag, use chainfire 3D etc or go for a custom mod!
Is there a similar app for modded roms's like chainfire 3D to help game perfomance on this limited hardware? I'd really prefer to use a modded rom and build up from there, but as I stated earlier in the post, this will be used only for games and listening to music from youtube, so i'll maybe have to research some more to find out what would work the best.
Many, many thanks for your help, I've learnt alot during this project!!
Oh as a bit of an aside, got a bit worried when downloading some of the links, some of the "download managers" were causing my anti-virus and anti-malware software to give me warnings!
Thanks again
@macsbig, Glad everything worked out for you mate . To address your concerns I must say that I did not come across any working solution for accelerating your GPU with reduction [email protected] custom Roms unfortunately ( only works on stock fw/rooted device) .
For CM9 beta Rom available @ development sub forum , this is an unstable Rom with some serious problems , because of ICS bugs an other things( Read this troubleshooting session and links provided there ).
For malware's concerns they are mostly false positives . Even virus total wold miss lead you in many cases, due to nature of advertising agent implanted inside some of the app inside system directory of custom Roms . You can simply replace the app in question with another one free of adverts. However they are harmless mostly. Please read this discussion (post #472-475) (post#291-298) between me and moderators team for more information about advertisement policies. Basically we have a very good control over materials presented here , thanks to mod teams .
Hope I did help you with your quest
My apologies, when I said that I was getting anti-virus/malware warnings, that was aimed at when I was trying to download the files on "mediafire(?)" and such like. They want you to install a stupid downloader etc., which then installs some crap on your pc.
Had it when downloading splitfus2 if I recall correctly (it was late 12am!).
That's why in the end I decided to use a pre - split (is that what you mean by wiped?) rom in the end.
I'm gonna have a play with the 'phone again later when I finish work.
Just found a beautiful ROM on 4pda forum. The ROM is developed by user booroondook. A few specifications, thanks to Google translate:
- DIY kit for all resolutions/platforms (well, all means RK3066 or RK3188 and the two main resolutions our units support). Just download the archive and run the setup script. Warning! Lollipop ROM only for RK3188!
-FUSE support - File system in User space. internal_sd is part of /data
-OTA system updates
-mostly untouched UI
-support for SD-card located startup script
For my GA2114 this is the most stable ROM to date.
The install procedure a little bit long-enter recovery, install, reset, enter recovery, install again, wait a long time for the intialization scripts to end. When done, enter settings and change the language to English as default is Russian - by far the most complicated part of the setup
You can take a look at it here.
A more detailed install procedure in this post
Latest KitKat build from March 2016 HERE
NEW Lollipop build - March 9, 2017 :Details and download link
Personally I need more info before installing this one. Perhaps Malaysk can comment on this rom
That ROM is significant step forward with FUSE. Installation is not problematic - it justbit strange. You have to install TWICE! First time, after initial boot, the new system partitions and links and file-system permissions are setup (this step cannot be done in recovery during initial firmware update). Then, for redefined OS and file sys mapping, SECOND firmware update (without wipping!) sets up everything in adequate locations (with FUSEd linkage among storage volumes). As you may figure out, you should let device to reboot after first install, but you dont have to let it go into full loading as it will usualy stuck (because needed foles are messesd up as the SECOND install is needed to put them in FUSEd locations).
So if you have problem with Russian and Google Translated very strange output, just do as above. Two times install ROM image. And its all fine.
Now, on the poibt:
I hope Malaysk will pay attention on this. The FUSEd ROM is much advanced option to better utilize our ibternal storage than 2GB or even 4GB data partitions fixed resizing (which is huge improvement itself from idiotic 1GB OEM Chinese 'design' I'm pritty sure is just blind copy-paste from some seed OS image they took from somewhere and they even after several years dont understand at ALL).
So I would kindly ask Malaysk to consider joining efirt with his Russian coleague who did FUSE but is not updating nor customizing his ROM as much and as dynamicaly (and passionately) as Malaysk.
So if Malaysk can adopt, merge, FUSE in his ROM it will be great leap forward for everyone. Original FUSE contribution would continu to live and power up the great Malaysk ROM branch. A I hope other devs them may find interest to join efforts, to contribute to that UNIFIED branch ratger than we have nu.ber of branches, at different stages, with different strengths and weaknesses....
Learning from mature dev teams working for years on phone ROMs, it is important to join, coordinate, split in modular but UNIFIED and at the end combined ROM released. It provided much better results. And it pays off for both us, users, and devs (if we pay respect they deserve for their noble effort).
I will always stress that I personally feel interest to stimulate this community to develop and matture. I'm very disapointed by Chinese very poor SW support, but I have beleive that HW is much more capable. So if we can get advanced SW for these units, it may well pay off for ALL of us who bouth them for fraction of price of OEM ones. An even we can have much better SW and overal functionalities than OEM. So the price difference allows us to dinate deacent sums to devs here if they provided us with good ROMs.
manicuspanicus said:
Personally I need more info before installing this one. Perhaps Malaysk can comment on this rom
Click to expand...
Click to collapse
Well, it was Malaysk who actually gave me the idea to look for these ROMS, in this post he mentions the other cooks.
Yes he did in a post where people want different colour on his rom . What I'm saying is I would like to know more like the description Malaysk has in his roms. Is it a big deal to ask you to give us a review of the rom and a step by step guide on installing it if there are some different steps from all the other roms?
Στάλθηκε από το ONE A2003 μου χρησιμοποιώντας Tapatalk
As I wrote, ROM us stock modded to have FUSEd partitions for data. Stabile as stock, looks like stock, perfirms as stock...
I explained install procedure as it is but strange and someone NOT knowing Russian may be buzzed with Google Translation (thinking it is transkation mistake to have double install needed).
But the real problem here us that devs are not joining and coordinating efforts. So we have Malaysk point insatisfied users to other ROMs... When dev starts to divert users to other ROMs, it looks something is wrong here, isnt it?
manicuspanicus said:
Yes he did in a post where people want different colour on his rom . What I'm saying is I would like to know more like the description Malaysk has in his roms. Is it a big deal to ask you to give us a review of the rom and a step by step guide on installing it if there are some different steps from all the other roms?
Στάλθηκε από το ONE A2003 μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
I can do that, no issue. Just give me a couple of days. It's the least I can do for fellow xda members
FUSE seems to be the right way to go, i hate the fact that as standard i can only use 1gig for user data, and i also don't want to decompile and replace the file for partition and recompile every time i want to update/change rom etc etc.
So i hope Malaysk will pick it up and some proper documentation written by someone
m00n61 said:
I can do that, no issue. Just give me a couple of days. It's the least I can do for fellow xda members
Click to expand...
Click to collapse
:good:
Booroondook DIY ROM details
WARNING! Make sure you can boot into recovery even with the screen off. This will allow you to install a factory ROM if anything goes wrong.
Back up your user data. This ROM has to format the internal Flash so all user data will be deleted.
DISCLAIMER. I am not affiliated in any way with the developer of this ROM. All credits should go to 4pda user Booroondook. I only wanted to share this ROM that works perfectly for my unit, keeping the OEM flavor and vastly improving on functionality - yet is pretty much unknown due to language barriers.
Preparing for installation
1. Download the DIY kit to your computer. Unpack into any empty folder on your computer (the full path to the folder should not contain spaces, non-Latin characters, punctuation marks and special characters, so it is not recommended unpacking on the desktop, in the "My Documents"folder, etc.
2. Switch to the folder where you unpacked the archive.
2. Run start_eng.bat. Since you are reading this HOWTO I assume you are not familiar with Russian.
3. You will be prompted to select a processor. Only two options - RK3066 and RK3188. The selection is made by entering the numbers in front of said processor type, followed by pressing the Enter key
4. Next - the choice of screen resolution. There are also two variants - 800x480 and 1024x600. Selection is carried out in the same manner as in the preceding paragraph
5. After that begins the process of assembling the firmware, which takes less than 10 seconds.
4. Wait for the ROM to be prepared and, when done, exit the batch file.You will have a new file, called update_yourprocessor_yourresolution.img
5.Rename the generated file to update.img
6. Copy the file to an SD-card
Installation
1. Insert the Sdcard containing update.img in your HU.
2. Boot into recovery. On my unit I can do that in two ways:
a. Press the reset button. Keep ot pressed while also pressing the Power button. Release the reset button and keep the power pressed a few more seconds
b. Press the reset button. Press both Home and Power buttons for about 10 seconds (the button light will flash shortly) and release the Home button followed by releasing the Power button then pressing Power again .
2. Do a factory reset - the last option in the list - to clear data and cache
3. Update the firmware. Wait for the unit to reboot.
4. Whe you see the animated logo, reset the HU and re-enter recovery mode
5. Update the firmware again. Wait for reboot
6. The first start will take longer than usual due to the need to re-create the primary filesystem and running of initialization scripts.
Release notes:
Base firmware: HA-20151010
Initial DPI is set to 160 for 800*480 screens and 240 for 1024*600. You can change this in Settings
Initial language is set to Russian. Just go to Settings (you should recognize the icon) and look for язык - this means language in Russian. Click on that and change to your preferred language.
In the release notes, Booroondook says the ROM has USB debugging enabled which will prevent using a USB stick. I don't have that issue so maybe the article is outdated. Anyway, if you have this issue, either type ADBOFF in factory settings password field or delete the file /system/etc/init.d/01adbon
Custscript
If the root GPS-card contains a file with the name custscript, it will be executed when you start the HU.The requirements for the file are the same as in conventional Linux executable scripts. That is, an indication of the shell in the first line and the line breaks Unix-style.
The first line can be: #! / System / bin / sh
For example, if you are experiencing problems with the rebooting in recoveryi (no suitable hardware buttons, or other reasons), then you could put on the card a file with the following content:
PHP:
#! / system / bin / sh
reboot recovery
And your HU will reboot in recovery mode. However, don't forget to delete it when done.
This script can also be used for "early loading" applications and services.
The advantage of the script placed on the SDcard is that unlike install-recovery.sh, if something went wrong, you can simply pull out the card to fix the script. In addition, in some cases, through a script, you can "revive" the HU.
Other features - in no particular order
1. FUSE - no need for App2SD since all space is available for apps or data;
2. OTA system updates;
3. Both OEM launchers available - not in the initial kit, appeared after a second OTA;
Screenshots
Excellent job !
Booroondook is on XDA also, hes posted a good few times in the "original thread" (RIP - the thread, not Booroondook !).
I was aware he used to make ROMs for these units, but this past year its all been about Malaysk's, not heard anything about @booroondooks's.
bootloop after instalation
Great rom in the first half hour
same here
zorantoma said:
Great rom in the first half hour
Click to expand...
Click to collapse
Mine won't even fully boot after the 2nd update from recovery..Good to see that its not just me..
Edit
Tried with a newly created image from the Bat file.
Still looped but I was able to get it to work from the recovery screen by using the "reset to factory/clear data option"
After that the setup script worked.
New version is out
New version is out, based on HA-20151204. Get it here.
The following is taken from the author's post on 4pda:
Since the original is only for RK3188 / 1024x600, the kernel versions for other combinations of CPU and resolutions are from earlier firmware:
RK3188 / 800x480 - from JY-20150824
RK3066 / 1024x600 - from HA-20151010
RK3066 / 800x480 - from KLD-20151127
New features :
1. Two factory launcher - "HA / JY" and "KLD" - you can change the settings (Display -> Desktop). Both are fully functional (weather, radio, music, Bluetooth)
2. Support for trip computer "Multitronics MPC-800" - no need for Xposed module
3. Changes to preinstalled applications in the "OEM" section:
3.1 preinstalled applications (can be completely or selectively removed (Settings - Applications)):
- Chrome
- Root Explorer
- Terminal
- Titanium Backup
- True Contacts
- DPI Changer
3.2 Preloaded set of Xposed modules
3.3 APKs for manual installation ( OEM ):
- AirPin PRO
- CarService 2.1.3
- DAB
- EasyConnected.HT01.4.0.4-151012
- GScript_v.1.1.2_Rus
- Headunit 2.15
- IOnRoad.apk
- Multitronics_2015-12-24_beta
- RemoteADB
- Torque
- TPMS
4. Removed DPI change from the "Settings". Added app "DPI Changer" (pre-installed)
Hi @m00n61,
Is the version you just posted the one for 1024x600 rk3188?
If I understood well, have to install that twice?
Thanks!
magnificus said:
Hi @m00n61,
Is the version you just posted the one for 1024x600 rk3188?
If I understood well, have to install that twice?
Thanks!
Click to expand...
Click to collapse
The link is for the so-called "constructor" that can generate the Rom for your CPU/resolution combination. Just follow the steps in the first post to generate the one you need.
If you come from stock or another ROM, yes, you have to install twice and clear data/cache before and between installations.
If you already have the previous version installed then you only need to install once and it will be upgraded, keeping all your apps.
Im still new to MTCB, will this rom work on my Eonon GA5151F? http://www.eonon.com/Car-GPS/Specific-Car-GPS/Mazda/GA5151F.html
Thanks in advance
SkiRac3rDud3 said:
Im still new to MTCB, will this rom work on my Eonon GA5151F? http://www.eonon.com/Car-GPS/Specific-Car-GPS/Mazda/GA5151F.html
Thanks in advance
Click to expand...
Click to collapse
It should work. looks like you have a RK3188/800*480 unit. To be sure, go to Settings ->About tablet and check the 3rd line. If it starts with MTCB, this ROM will work for you.
What about RK3188 with 1024*600? I only see 1024*600 for RK3066, not for RK3188...
m4f1050 said:
What about RK3188 with 1024*600? I only see 1024*600 for RK3066, not for RK3188...
Click to expand...
Click to collapse
Well, post #14 says:
"Since the original is only for RK3188 / 1024x600, the kernel versions for other combinations of CPU and resolutions are from earlier firmware."
So yes, it's there.
UPDATE: I was able to debrick the phone. Read my later post for details.
----------------------
Hi All,
Thank you all for having amazing community of hackers and developers here. You guys rock.
I started my search for a new rugged rootable phone recently and I settled on Poptel P60. It is a great phone though slightly bigger than what I normally get. Nontheless, the specs are excellent and the price is fair!
I've had a limited success rooting and customizing this phone. The OEM interface is almost bearable but overall the "Customized UI" felt like a downgrade from stock Oreo. It has a very annoying feature of reverting to stock launcher on startup, even when I selected Nova as my default one. The stock launcher is not that great. This, and the lack of ability to use x.flux, Titanium Backup and other root-only apps drove me to try hacking things again.
After emailing the manufacturer they provided the firmware but it is in CPB format. I tried at least 3 different converters for CPB to MTK Scatter and they all either freeze or hang. No luck.
Instead I did a rom readback with SPFlashTool and then cut up the partitions with Wwr. Now I've finally had the recovery partition! I used CarlivImageKitchen to port TWRP from a similar device, Ulefone Armor 5. The chipset and resolution are same. After some trial and error it worked! I had to use USB-OTG for input and external sd card had a weird label, but I was able to install Magisk from the SD card to root, followed by XPosed, full package. It worked! If anyone needs my ported TWRP Recovery for Poptel P60 just ask!
However, the manufacturer UI did complain a lot about the phone being rooted. Eventually, somehow, Magisk stop receiving root requests. They never showed up and timed out! Very strange, because apps that already received root continued working. I tried a lot but could not fix the issue. I was fed up. I wanted to do a manufacturer reset (in hopes of starting from scratch and then attempting to port Lineage or something) but, as I've mentioned, I have not received a firmware compatible with SPFlashTool. I tried to make one from Armor 5. The partitions were almost the same (both are MT6763 devices). One was out of order, and offsets were different and I patched all those. To be clear, I used all the partitions and layout extracted from my rom readback that was cut up by Wwr. I only used the Armor 5 scatter as a reference for file format. I edited the layout to match everythign I saw in Wwr.
This is where the horror begins. I tried flashing (Download Only) with SPFlashTool but got some error saying something changed. "Do you want to do Format & Download instead?". Being an inexperienced idiot that I am, I said yes!
Now, the phone appears bricked. No lights. No screen output. Cannot enter fastboot. Cannot enter recovery. Cannot boot.
I have a feeling the preloader got corrupted. I'm not sure this is the case because I've omitted the preloder from download. At least the first time the phone started acting bricked. The device still shows as Mediatek USB VCOM device and flashing gets initiated but all attempts to flash result in errors. MA checksum mistmatch or something along that order. I've tried a lot of things and I'm stuck! For good or for worse I've tried flashing Ulefone Armor 5 preloader but I'm getting the same error when trying to flash it.
Here is what I have...
- Stock firmware in SPB format. I can't use it and nothing I tried worked for converting it.
- ROM dump made with SPFlashTool
- Wwr was able to extract every partition except preloader. This includes nvram, etc. I'm not sure why it was not able to extract the bootloader.
- TWRP port that worked. Seems not useful if the phone does not start.
- Preloader for Ulefone Armor 5, (same chipset and resolution)
Clearly I am an idiot for using "Format & Download" option. I've found posts later suggesting against it. I am also over my head for trying to tackle a new device by myself, though I have had a marginal success with porting TWRP and installing Magisk.
Now, I feel like idiot and I am stuck! I beg you, XDA developers, if you have any advice (besides not being an idiot in the future), please share!
Try bringing it back to the carrier and just say that you don't know why it is broken. Maybe they could help you out.
Say maybe something like you wanted to do a factory reset and now everything is broken.
SkylinesHD said:
Try bringing it back to the carrier and just say that you don't know why it is broken. Maybe they could help you out.
Say maybe something like you wanted to do a factory reset and now everything is broken.
Click to expand...
Click to collapse
That wouldn't work, heh. I bought this phone on eBay and rights now it's currently sold by a handful of sites. It is on warranty but returning it back to China would be complicated. At any rate, I live on the edge outside of warranty!
I was just about ready to give up and feel like the biggest reckless loser on Earth... Days of tinkering around with nothing but a phone brick to show for it. Poptel tech support wouldn't provide me with MTK scatter. All they gave me was this SPB firmware that nobody uses and it crashes every converter I threw at it. Useless.... No fastboot. No recovery. No functional bootloader.
The amazing GOOD NEWS is I have debricked the phone... I used a bootloader from another phone's firmware: Cubot_Power_MT6763_180607_8.1.0. Unlike Ulefone Armor 5's preloader this one worked! It seems like it's the only thing I was missing because the phone starts up and everything seems to work. I must have done a good job with all other partitions but I'll try to watch for signs of anything else broken. Right now it seems fine.
I'm not sure if the bootloader was completely gone, corrupted, or an incorrect one was used. All I know is I was able to download Cubot Power's working bootloader (also MT6763) with SPFlashTool. Nothing like a feeling of unbricking your phone!
I will post more updates if that's ok... I'm hoping to port Lineage on it (I've never tried that before) or at least find a way around the manufacturer's clunky UI. The hardware is great otherwise. If anybody wants a working ported TWRP image or the scatter I used for debricking just ask! I will make a post later if I have more success with customizing the phone. The phone is debricked and I have a scatter and images to fall back on if anything goes wrong. Woot! Thank you everyone who developed these great tools.
I have the same phone been looking for info. there's a thread on 4pda with poptel p60 that has the scatter file and firmware. Any chance you could post the twrp for this phone? having trouble trying to port myself cant figure out port 6763 from the guides available.
4pda.ru/forum/index.php?showtopic=933002
Firemware:
drive.google.com/uc?id=1PXA9s2ZgHoH6ZWP5ZJPckE4KyJBwPKuw&export=download
idaman0 said:
Hey man,
Was wondering if you saw my post on your thread. Looking for TWRP for the Poptel P60.
Thanks,
telegram @drmethyl
Click to expand...
Click to collapse
Hey man! Sorry for a slow reply. Was traveling for a few days.
Here is what I have. I started with a TWRP for Armor 5 (also MT6763) and I ported it for Poptel P60 using one of the guides on the forums. It works but it's not perfect. The touchscreen doesn't work, so you have to use USB OTG. Also, internal and external SD card mounts work but labels are confusing, so please be extra careful if wiping/formatting those. I advise popping the SD card out of the phone if wiping/formatting, just in case.
My experience with the phone is it is not the most friendly for rooting. Poptel's customizations are pesky and get in the way. The launcher keeps resetting to default on startup, even after you specify a different one. If you uninstall/disable the OEM launcher there will be red a label on top right of the screen, saying "Customization" that I have not found a way to get rid of. There are other things too, like I keep losing ability to add superuser permission to new apps... Can't figure out why, but sometimes reinstalling Magisk helps. Be very careful when using Magisk Hide, this can turn off your ability to use SIM cards, at least temporarily until you disable hide and restart. Other things is superuser apps don't always launch on startup. Anyway, I don't want to discourage you too much... Here is my twrp port.
https://mega.nz/#!MNVGhaYS!63ovQeowwoP1oE3v6-_ZS8gKx_-mxOh4G4qWcKRbuiQ
Another thing I discovered is GSI builds work mostly well on the phone... with all except one thing, which is mobile data, which seems broken.. Sadly, that's a deal breaker. OEM software is so pesky... It would be so nice to run a clean Android.
Let me know how it goes.
zeromemory_wtf said:
Hey man! Sorry for a slow reply. Was traveling for a few days.
Here is what I have. I started with a TWRP for Armor 5 (also MT6763) and I ported it for Poptel P60 using one of the guides on the forums. It works but it's not perfect. The touchscreen doesn't work, so you have to use USB OTG. Also, internal and external SD card mounts work but labels are confusing, so please be extra careful if wiping/formatting those. I advise popping the SD card out of the phone if wiping/formatting, just in case.
My experience with the phone is it is not the most friendly for rooting. Poptel's customizations are pesky and get in the way. The launcher keeps resetting to default on startup, even after you specify a different one. If you uninstall/disable the OEM launcher there will be red a label on top right of the screen, saying "Customization" that I have not found a way to get rid of. There are other things too, like I keep losing ability to add superuser permission to new apps... Can't figure out why, but sometimes reinstalling Magisk helps. Be very careful when using Magisk Hide, this can turn off your ability to use SIM cards, at least temporarily until you disable hide and restart. Other things is superuser apps don't always launch on startup. Anyway, I don't want to discourage you too much... Here is my twrp port.
Another thing I discovered is GSI builds work mostly well on the phone... with all except one thing, which is mobile data, which seems broken.. Sadly, that's a deal breaker. OEM software is so pesky... It would be so nice to run a clean Android.
Let me know how it goes.
Click to expand...
Click to collapse
sorry man, didn't end up using yours theres a twrp on 4pda now with a mod to flash to keep root. I'll upload for you here if you don;t have an account there.
The patch for the Light-kastomizator v.12 factory firmware.
I decided not to bother with the draining and distribution of modified firmware as a whole, easier to apply the patch, and ... you're done!
If that - the factory firmware v.12 lies with us -HERE, no problem you can return everything back, or (if there is something Kolupaev), first ask her, and then patch.
#
What is done
Будут удалены:
/system/tts
/system/app/QK_LogSystemAbroad_wm_bl
/system/app/QK_Sos
/system/app/QK_PrivacySpace
/system/app/QK_PersonalAssistScreenAbroad_V2
/system/app/BY_3RD_OperaMiniBrowser_OEMBranding
/system/app/BY_3RD_OperaNews_OEMBranding
/system/app/Drive
/system/app/Duo
/system/app/Gmail2
/system/app/GooglePrintRecommendationService
/system/app/LatinImeGoogle
/system/app/Maps
/system/app/Music2
/system/app/PartnerBookmarksProvider
/system/app/Photos
/system/app/YouTube
/system/app/Videos
/system/presetapp/BY_3RD_OperaMiniBrowser
/system/presetapp/BY_3RD_OperaNews
/ system / priv-app / MtkCellBroadcastReceiver
/ system / priv-app / ConfigUpdater
/ system / priv-app / GoogleFeedback
/ system / priv-app / FilesGo
/ system / priv-app / GooglePartnerSetup
/ system / priv-app / QK_MagazineAbroad
/ system / priv-app / Velvet
The system additionally installed:
ES_Provodnik_3.2.5.5 (graphic mode "Panatta-sport")
the SD Maid Pro - system Cleanup (Lite Mod "Breathe of fate" )
Changes:
By default the system is set to Russian language , region and time zone Russia / Moscow. Setupwizard (first assistant settings) is not cut off.
GBoard keyboard replaced by fashion Antonbeard GoogleKeyboard(with a limited access to the Internet is built dictionaries -.. English and Russian)
Google-search is replaced by the latest beta (it is possible to change the style and transparency of the widget)
have been added and changed some default sounds and ringtones, and the default there as a very sadly.
Blocked by advertising the hosts file.
Improved energy efficiency due to shutdown of background update service does not fall asleep GAPPS and downloaders (allowed these services Doze mode).
#
Setting:
1. Throws on micro SD-card this patch.
2. Downloading the last zip-installer " Magisk-v ..... the zip " and also copy it to the SD-card, turn off the phone.
3. Through the SP Flash Tool sewn recovery "TWRP" (the system can not be loaded !!!).
4. Vaypaem userdata (reset to factory settings) through better "factory mode" (volume down inc +) / select "Clear eMMC".
After reset immediately loads in the TWRP (inc + volume up), and from the sd-card in turn apply patches "LiteMod_Poptel_P60_v.12.zip" and "Magisk-v ..... zip". Reboot from the installation refuse twrp-applications.
Done, you have custom firmware!
(If twrp and Ruth is already installed,
After the completion of all the manipulations, it is desirable to flash the stock (factory) rekaveri, then no problem can be used to reset the system from the Android menu and install the firmware update OTA (over the air).
Download: LiteMod_Poptel_P60_v.12.zip
PS. Sberbank + contactless payment working properly, despite the fact that the system has been modified and installed Ruth! :derisive:
Click to expand...
Click to collapse
3.2.3 TWRP by Jemmini for "Poptel P60" ( with the phone port Blackview BV9500): Attached file recovery.img (17,27 MB)
The port used by the kernel to flash Android 8.1.0 version of "POPTEL_V12_20181030"
WARNING !! After installing recovery, subject to permit changes in the system partition, install ROOT is required, otherwise the system will not boot. if not to accept the possibility of changing the system partition and establish the patch-root subsequent restart in overwrite TWRP recovery returned drain-
Attached fileMT6763_Android_scatter.rar(1.28 kb)
#
Getting ROOT
For ROOT set out under TWRP (pre throwing off the memory card), this patch: Attached fileMagisk-v18.0.zip (3,99 MB)
#
Stokovye boot / recovery
from said EEPROM: Attached filestock.rar (22,75 MB)
#
What does not work:
1) Do not see "the internal memory" (can not decipher the "data" section and ask when starting TWRP password).
Solution:
download the patch: Attached filedisable_encryption_P60.zip (133.89 KB)
throw it on the memory card, boot into TWRP, go to the "mount" to put a checkbox on the vendor , then go to the "install" and install the patch.
After installation make data in the "cleaning" cleaning (possibly cleaning does not help but the formatting of data should definitely help)
after data manipulation TWRP be able to work with the data section
2) is not working USB / MTP mode into TWRP
#
Information for those who are "in the tank" :
When TWRP presence in the smartphone in any case and under no circumstances should you do reset through the system.
Resetting takes place only directly through TWRP (standard cleaning sections)
If you run the command via the android in the first place, it can not be executed because it does not understand the TWRP.
and secondly, you get a constant load in TWRP because it has not yet executed the command android you will always be send to recovery /
Solution for "tank": need to install flow-recovery to be completed through a reset command or cancel it.
Another solution I personally do not know
Just do not forget about gratitude : Jemmini,- for the compilation of the TWRP which served as donorUrree,- order TWRP and testing (nothing would have happened without it)Message edited Lomaster_Serg - 6.1.19, 03:02
Click to expand...
Click to collapse
rapidgator.net/file/84ccd2d612ade0256eb927895d4ed37e/LiteMod_Poptel_P60_v.12.zip.html
rapidgator.net/file/c77fec40e349f8083eda14bf7058425c/recovery.img.html
rapidgator.net/file/6621d517cef9aa10abc78b40bcdc8b26/stock.rar.html
rapidgator.net/file/7a7db29c0d35eee169b76698aac6b50b/MT6763_Android_scatter.txt.html
drive.google.com/uc?id=1PXA9s2ZgHoH6ZWP5ZJPckE4KyJBwPKuw&export=download