Finally my Galaxy nexus was broken beyond repaired, so it was time for new phone.
Since I am living in Panama, the only option was to get G2 d805 from Cable and Wireless.
Here the result:
Flashed root using this link
http://forum.xda-developers.com/showthread.php?t=2448887
Interesting part that is flashed ok and put su, but when I start using Root explorer and Titanium backup, it’s never pop a message, but everything was working fine.
Then installed TWRP using d802
http://forum.xda-developers.com/showthread.php?t=2469995
and then from installed recovery installed d805 variant
After all done, I have backup EFS, using this
http://forum.xda-developers.com/showthread.php?t=2451390
After all done its time to flash ROM:
Installed this ROM
http://forum.xda-developers.com/showthread.php?t=2483702
Since I do not care about LG software, I have installed light version.
For 3 days worked not problem whatsoever
Then installed this ROM MOKEE
http://mokee.basketbuild.com/index.php?dir=main/NIGHTLY/d802/
this is 4.3 ROM also working no problem.
Note:
Since I am on CWPanama, I can only use 3G, so out of curiosity flashed this modem
http://http://forum.xda-developers.com/showthread.php?t=2451426
D80310c-RGR
M8974A-AAAANAZM-1.0.190036
by QUALCOMM, Incorporated Sept 4 2013
And this modem:
D80210b-EUR-XX
M8974A-AAAANAZM-1.0.190036
by QUALCOMM, Incorporated Sept 6 2013
Since I am on 850 3G, found out that 803 modem work a little bit better, then original 805 or 802.
Unfortunately I cannot test LTE.
So to my conclusion all 802 / 803 ROM working fine on 805 variant.
Restore all my app (no system app) using latest Titanium as no problem, only BBM detect another hardware and assigned new PIN.
Next week i will test more d802 ROM running on d805 phone.
P.S.
Forgot to mention some of the ROM from d802 will generate this during attempt to install.
assert failed: getprop("ro.product.device") ==
Workaround:
You do this with 7-Zip/WinRAR
Note: DO NOT EXTRACT ROM!
In the ROM go to:
/META-INF/com/google/android/updater-script
1)Open updater-script with a script editor such as notepad/notepad++ (makes things 10x easier), or gedit if you use linux
2)Delete the first line of code (all the way up to the first semicolon you see) and delete the first semi-colon as well
Do not go past the first semiclon when deleteing and DO NOT forget to delete the first semicolon.
thanks
I buy this equipment in COLOMBIA and I think it's great that you can install ROM D802.
Aosp you can install all d802 variant, i recomend paranoid 4.0,my device is d805 too.
Sent from my LG-G2 using XDA Premium 4 mobile app
I don't wanna install any rom of 802 cause i won't brick my device, but with your post maybe i will do it.
Im from Panama too jaja
Sent from my LG-D805 using xda app-developers app
Thanks for the info, it is difficult with so many versions, altough stock is really good for now.
Sent from my LG-D805 using xda app-developers app
I Flash the rom lite that you post in your first comment, it works, perfectly, i have a question, my firmware version at config appears like the first rom, but model has changed to 802, the boot animation still like the rom oficial of my operator, but, the compilation number is the updated.
I will told you more before some tests.
Hi Guys , any custom Kernel for the D805 rooted Model? Im on OEM android Version. THanks
Guys please post here when/if the D805 variant gets the official kitkat upgrade. Thanks in advance.
Related
Hello every one,
So after some long time saving, I finally have enough to buy an LG Optimus G from my friend. His phone (mine now) is great and work flawlessly. Today I decide that I will go for a little adventure and flash new kernel to oc my phone (currently running stock 4.1.2). When going to fastboot, I saw the following
Fastboot Mode
Product name - mako
Variant - mako 16GB
HW Version - rev_10 (16)
Bootloader Version - MAKOZ10o
Baseband Version - N/A
Carrier Info - None
Serial Number - <Something unrelevant>
Signing - production
Secure Boot - enabled
Lock State - unlocked
Click to expand...
Click to collapse
After some search, I knew that "mako" is meant for Nexus 4, right? So is this mean my phone is an N4 converted? It's really weird that it can still regconized the SD card.
I've do some search on google, and on xda but still not get the answer I need. If there is any duplication, please forgive me .
Thank you very much ^^
Pretty sure any phone running 4.2 and above.. Roms, bootloader, kernel.. Have the mako branding.. I have it and have never done the conversion.
Yours might be converted as well. I wouldn't know the difference.
Sent from my LG Optimus G using xda app-developers app
Mako discussion
The reason behind your phone mako bootloader is that Optimus G At&t and LG nexus 4 both shared same hardware and built that means you can also convert your Optimus G At&t into full fledged Nexus 4 minus external built. I posted the link below that explains how to do conversion.
But remember this conversion will only work on Optimus G At&t version.
http://forum.xda-developers.com/showthread.php?t=2099784( For converting Optimus G into Nexus 4)
http://forum.xda-developers.com/showthread.php?t=2160124 ( For converting 8GB Nexus 4 INTO 16 GB)
Thanks
Thank you for clarify that matter . I don't intend to convert to N4 anyway. To me, the micro SD worth more than running latest software .
More than that, a lot of roms have been ported to geeb, I intend to do some myself . Science if fun :v
Thank you for clarify that matter . I don't intend to convert to N4 anyway. To me, the micro SD worth more than running latest software .
More than that, a lot of roms have been ported to geeb, I intend to do some myself . Science if fun :v
It may just be that your bootloader is unlocked, the FreeGee method uses mako bootloader.
which rom did you install GPROJ or a GEEB?
Hi, all,
I recently helped an acquaintance that was having a terrible time with an assert_failed error with Loki while trying to install CM 10.2, so I figured I'd explain the problem and solution.
Backing up to the beginning, this acquaintance recently upgraded to the G2 (a few weeks ago) and wanted to test out KitKat. Here, we discovered that the phone had been updated to VS98012b before he'd received it - but rather than reverting to stock, we decided to use the root solution detailed here (http://wiki.cyanogenmod.org/w/Install_CM_for_d802), but we swapped the Loki flash method to that detailed here (http://forum.xda-developers.com/showthread.php?t=2449670) and used the CWM no-touch image from here (http://forum.xda-developers.com/showthread.php?t=2498941). [For reference, the touch image doesn't flash properly... but the one without touch is still touch-enabled.]
After gaining root and getting CWM up and running, we decided on the Nightly CM 11 build (ro.build.date=Sat Jan 18 08:04:40 PST 2014) and it flashed with the recommended GApps without a hitch.
Fast-forward three days and said acquaintance is having tons of crashing issues and some apps weren't working too well - certainly not far-fetched for a nightly build. We decided to flash him back to CM 10.2. However, after doing a factory reset, wiping the cache again to be sure, then wiping the dalvik cache, and finally running the CM 10.2 stable version available here (http://download.cyanogenmod.org/get/jenkins/49892/cm-10.2.0-vs980.zip, date: 2013-12-02 21:45:13) we ran into the following error during the install:
Code:
script aborted: assert failed: run_program("/tmp/loki.sh") == 0
assert failed: run_program("/tmp/loki.sh") == 0
Neat.
Some digging lead to a Pastebin (http://pastebin.com/uLtw2vG6) with an explanation of the problem and a proposed solution:
Code:
[email protected] : autoprime, thats 9/10 times because old loki_patch
...
[email protected] : if they are stuck in recovery completely because they wiped everything then just remove the assert line you meniotned and flash the rom then flash the zip I just linked
Since I've poked around with ROMs before, I unzipped the CM 10.2 ROM and popped the /cm-10.2.0-vs980/META-INF/com/google/android/updater-script file open to remove the assert line and the deletion line, incidentally. But reflashing the ROM and the linked zip that Shellnutt2 suggested (http://downloads.codefi.re/shelnutt2/freegee/loki_boot.zip, for the curious) didn't actually work for us. Much of the problem, I suppose, had to do with the data and system partitions not being loaded in the loki_boot.zip updater-script.
So a bit of thought lead me to check the CM 11 commits for updates to enable functionality for the VS98012b update - bingo! A conveniently close-to-the-top update (http://review.cyanogenmod.org/#/c/56181/) mentioned that, as Shellnutt2 suggested, loki_flash was updated for this precise reason. Now, I wasn't about the pull the whole CM 10.2 repo and build with the updated loki_flash.c, so I just copied the newest CM 11 nightly's /system/bin/loki_flash, /system/bin/loki_patch, and /system/bin/loki.sh into the CM 10.2 ROM's /system/bin/ and overwrote the old ones (after reverting the updater-script changes, of course). After rezipping, the install worked like a charm!
---
[TLDR]
If you're having
Code:
script aborted: assert failed: run_program("/tmp/loki.sh") == 0
assert failed: run_program("/tmp/loki.sh") == 0
errors,
1) grab the latest CM distribution and copy the loki_flash, loki_patch, and loki.sh files out of /system/bin/ (or from https://www.mediafire.com/?y3ubxgnxzxq89f9, which are from the Tue Jan 21 13:05:13 PST 2014 CM11 Nightly) and
2) paste them over the /system/bin/ equivalents in whatever VS980 ROM you're having problems with,
3) rezip,
4) and clean flash the ROM in recovery.
Presumably, this workaround should work for all VS980 ROMs (tested for CM10.2 and OSE) that haven't updated their loki_patch versions. It probably won't work for any other phone that has loki.sh failed assertions - the GitHub master loki repo (https://github.com/djrbliss/loki/blob/master/loki_flash.c) doesn't say anything like the CM 11 distro, so it's likely a check coded in. But I didn't take the time to look into that on the CM side.
EDIT: This should also work for devices other than the VS980 - I looked up loki_flash.c rather than loki_patch.c (https://github.com/djrbliss/loki/blob/master/loki_patch.c) and incorrectly commented on the situation.
Any phone/software version found in the CyanogenMod 11 Repo listing for loki_patch.c (https://github.com/CyanogenMod/android_device_lge_g2-common/blob/cm-11.0/releasetools/loki_patch.c) file - do a CTRL+F - should be able to apply this workaround to flash a ROM with an out-of-date patcher.
EDIT 2:
This solution should, based on the Loki source used for CM11, work for the following G2 models:
AT&T: D80010d, D80010o (however 10o has a reported failure and no successes)
Verizon: VS98010b, VS98012b
T-Mobile / Canada: D80110c or D803
International: D802b
Sprint: LS980ZV7
KT / LGU: F320K, F320L
SKT: F320S, F320S11c
However, if you're just looking for a CM 10.2 ROM with this fix for the Verizon VS980, I uploaded the zip that I flashed for my acquaintance for convenience: http://www.mediafire.com/download/tmu28ihn3gm2ngw/cm-10.2-vs98012b.zip .
[/TLDR]
---
Hope this helps anyone that's having the same problem - good luck flashing!
Is the Loki patch updated for 12b backward compatible with 11a and so on?
Basically, would one on 11a, be able to flash a ROM with the 12b Loki patch?
Great write up by the way
VS980
If you're looking for a stable AOSP kk ROM try cyanfox. Its cm based. I've been running it for about 3 weeks with paeks kernel and have 0 probs with it. No lag no crashes no lockups no sods. Its been the most stable AOSP ROM I've found.
Sent from chdhsheh fhhdud
I've been having the same problem with the AT&T G2 on 10o. Besides downloading, do you think this will work for any of those roms?
Sent from my LG-D800 using xda app-developers app
Dork6243 said:
Is the Loki patch updated for 12b backward compatible with 11a and so on?
Basically, would one on 11a, be able to flash a ROM with the 12b Loki patch?
Click to expand...
Click to collapse
Skizzy034 said:
I've been having the same problem with the AT&T G2 on 10o. Besides downloading, do you think this will work for any of those roms?
Click to expand...
Click to collapse
The listed carrier/software variants in the current (Wed Jan 22 2014) CM11 G2 repo's loki_patch.c (and the uploaded loki_patch zip file) are:
AT&T: D80010d, D80010o
Verizon: VS98010b, VS98012b
T-Mobile / Canada: D80110c or D803
International: D802b
Sprint: LS980ZV7
KT / LGU: F320K, F320L
SKT: F320S, F320S11c
If you were to compile the current (Wed Jan 22 2014) loki_patch.c from https://github.com/djrbliss/loki/blob/master/loki_patch.c (sorry, can't post links because of new member restrictions) yourself, you'd get an added compatibility with:
DoCoMo: L-01F
On PURELY SPECULATIVE terms, there's a good chance other versions of the software for the different carriers could be supported if you download the Loki source and compile it after adding another entry (format shown below in code tags) for your specific carrier/software version. But I don't know anything about the code and have no reason to look into it, so I can't confirm this. Plus, I don't own a G2 myself and can't test this method anyway.
Code:
{
.vendor = "T-Mobile or Canada",
.device = "LG G2",
.build = "D80110c or D803",
.check_sigs = 0xf813294,
.hdr = 0xf906440,
.lg = 1,
},
feldenthorne said:
The listed carrier/software variants in the current (Wed Jan 22 2014) CM11 G2 repo's loki_patch.c (and the uploaded loki_patch zip file) are:
AT&T: D80010d, D80010o
Verizon: VS98010b, VS98012b
T-Mobile / Canada: D80110c or D803
International: D802b
Sprint: LS980ZV7
KT / LGU: F320K, F320L
SKT: F320S, F320S11c
If you were to compile the current (Wed Jan 22 2014) loki_patch.c from https://github.com/djrbliss/loki/blob/master/loki_patch.c (sorry, can't post links because of new member restrictions) yourself, you'd get an added compatibility with:
DoCoMo: L-01F
On PURELY SPECULATIVE terms, there's a good chance other versions of the software for the different carriers could be supported if you download the Loki source and compile it after adding another entry (format shown below in code tags) for your specific carrier/software version. But I don't know anything about the code and have no reason to look into it, so I can't confirm this. Plus, I don't own a G2 myself and can't test this method anyway.
Code:
{
.vendor = "T-Mobile or Canada",
.device = "LG G2",
.build = "D80110c or D803",
.check_sigs = 0xf813294,
.hdr = 0xf906440,
.lg = 1,
},
Click to expand...
Click to collapse
There is def. a problem with flashing roms on 10o.
Just as an update, Skizzy034's problem was apparently resolved by flashing the previous AT&T D800 firmware. (Presumably 10d.)
Perfect!
Thank you very much!!
I was having this exact error while installing 10.2, and your rom worked perfectly. Thanks!
Yeah buddy!
Thanks for the zip dude. ROM is running perfect. :good:
You have no Idea how much this helps
I thought I was totally screwed haha
Thanks for this! It worked out trying to get PAC-man ROM 4.4.2 for my D803. I just copied the loki files from another ROM.
CM11!
Oh man, I spent tons of time trying to find out what I did, and almost gave up. I switched to CM11 Nightly and it worked like a charm.
Latest CM 11.0 no longer contains loki_patch
The files in mediafire link that you provided didn't work for me, but I used the "loki.sh" and "loki_tools" files from a recent nightly build (cm-11-20141209-NIGHTLY-d800.zip) and it worked fine. loki_patch no longer is provided with cm-11, so I removed it from the cm-10.2 zip and my flash worked without it.
Thanks so much for posting this and helping everyone out with this problem.
Carl
Sorry folks if this is already somewhere here but i have not found it after already a few days of browsing.
I am looking for a lightweight (dont really care if vibeui, aosp, etc), stable (daily usage), fully working ROM (no problems with led notif, compass, etc), preferably 4.4.2. KitKat for chinese version of Lenovo P780 manufactured after 03/2014 and all other tools (custom recovery etc). What is essential, that i need to repartition the internal memory for maximum space for apps.
My current is 4.2.1 P780_S136_140306 , baseband : P780.V16, 2013/07/03 17:08 , i have a dtae on battery 140410 and 2014/05 on box. From what i gather this is a new 2014 version and on this one you should use ROMs based on 4.4 KitKat ??
So far i have found only two ROMs suitable, but not all criteria are met:
http://forum.xda-developers.com/lenovo-p780/development/slx-rom-lenovo-p780-t2722775 - based on 4.2 JB, so probably not working on new version ?
http://forum.xda-developers.com/lenovo-p780/development/alice-project-lenovo-p780-android-4-4-3-t2983584 - default memory partitioning
Any other suggestions ?
Is there any repartition script working for CN version (AromaFM working for CN version?), specifically for 03/2014+ version -- ?
So far i have found out for any flashing via SP Flash tools i need to use modified preloader http://forum.xda-developers.com/attachment.php?attachmentid=2934284&d=1410527296 -- check
I did not found any custom recovery specifically mentioning this new version, but it looks like recoveries working ok for this new version -- ? http://forum.xda-developers.com/lenovo-p780/development/recovery-multiple-recoveries-lenovo-t2962970
is there any specific version of SPFlash Tool and drivers to be used for this new version -- ? - i guess not but just to be sure, which are best to be used
Any modems to be flashed after flashing ROM (freqs in my country are GSM 900/1800, W-CDMA 1900/2100 ) -- ?
Any more thing i should be aware of ?
Dulus said:
Sorry folks if this is already somewhere here but i have not found it after already a few days of browsing.
I am looking for a lightweight (dont really care if vibeui, aosp, etc), stable (daily usage), fully working ROM (no problems with led notif, compass, etc), preferably 4.4.2. KitKat for chinese version of Lenovo P780 manufactured after 03/2014 and all other tools (custom recovery etc). What is essential, that i need to repartition the internal memory for maximum space for apps.
My current is 4.2.1 P780_S136_140306 , baseband : P780.V16, 2013/07/03 17:08 , i have a dtae on battery 140410 and 2014/05 on box. From what i gather this is a new 2014 version and on this one you should use ROMs based on 4.4 KitKat ??
So far i have found only two ROMs suitable, but not all criteria are met:
http://forum.xda-developers.com/lenovo-p780/development/slx-rom-lenovo-p780-t2722775 - based on 4.2 JB, so probably not working on new version ?
http://forum.xda-developers.com/lenovo-p780/development/alice-project-lenovo-p780-android-4-4-3-t2983584 - default memory partitioning
Any other suggestions ?
Is there any repartition script working for CN version (AromaFM working for CN version?), specifically for 03/2014+ version -- ?
So far i have found out for any flashing via SP Flash tools i need to use modified preloader http://forum.xda-developers.com/attachment.php?attachmentid=2934284&d=1410527296 -- check
I did not found any custom recovery specifically mentioning this new version, but it looks like recoveries working ok for this new version -- ? http://forum.xda-developers.com/lenovo-p780/development/recovery-multiple-recoveries-lenovo-t2962970
is there any specific version of SPFlash Tool and drivers to be used for this new version -- ? - i guess not but just to be sure, which are best to be used
Any modems to be flashed after flashing ROM (freqs in my country are GSM 900/1800, W-CDMA 1900/2100 ) -- ?
Any more thing i should be aware of ?
Click to expand...
Click to collapse
Hi. Did you try to OTA update your ROM? This could be the best ROM for you.
Or you can flash any rom here with flash tool, but do not forget to change preloader. For zip files there is no problem with the preloader because zip files are using the existing one.
Custom recoveryes you can find in Clarliv post i tested there one and is for China ROM VIBE UI 2.0. What can i tell: it is working.
SP Flash Tool for Lenovo P780 you will find in my post Rooting Tutorial for KITKAT. DO NOT USE OTHER.
For modems you have my post How about some modems.
stympy said:
Hi. Did you try to OTA update your ROM? This could be the best ROM for you.
Or you can flash any rom here with flash tool, but do not forget to change preloader. For zip files there is no problem with the preloader because zip files are using the existing one.
Custom recoveryes you can find in Clarliv post i tested there one and is for China ROM VIBE UI 2.0. What can i tell: it is working.
SP Flash Tool for Lenovo P780 you will find in my post Rooting Tutorial for KITKAT. DO NOT USE OTHER.
For modems you have my post How about some modems.
Click to expand...
Click to collapse
OTA updates are failing on my ROM , i guess they were disabled on purpose by the seller. Tried to repartition with http://forum.xda-developers.com/lenovo-p780/general/p780-repartition-storage-t2668744 but its not working.
Flashed back stock rom via FlashTools and i tried SLX ROM for CN version http://forum.xda-developers.com/lenovo-p780/development/slx-rom-lenovo-p780-t2722775 , but it always says that the PhoneStorage/SD card is damaged and you cant install any apps.
I have also tried latest official VIBEUI 2.0 (from here http://bbs.lenovo.com/vibeui-fabu/t542102/ in chinese ). It is actually pretty good and nice (only if thay used a stock app drawer and not the one like MIUI/iOS). But it leaves even less internal storage. And it does not have GAPPS and i was unsuccesfull to install these http://forum.xda-developers.com/showthread.php?t=2397942 (it said insufficient memory to install, although there was 1GB free on internal memory, propably a small system partition ??). I tried pico and nano.
-Actually if i was able to repartition for max memory and install GAPPS this will be a good option.
As for the recoveries i can confirm CWM based from Carliv's post works with this 2014 version. I will update his thread later.
I will try next the Alice project ROM.
Also i have a idea to use g00dvin's ROM http://lenovo-forums.ru/topic/6863-lenovo-p780-... for repartition and then flash official VIBEUI via recovery, if that will leave the partitions intact. And try different GAPPS if i will be able to install them
Modems will be last thing to mess with
Hi,
i was using Mokee 4.4.4 and since a few weeks I'm using Mokee 5.0.2
It is a rom like CM12 but with some customization, not as many as AOKP but still more than in CM12
It is multilangual and as stable as cm12
It was updated recently : http://www.yirom.com/rom/index/344
did someone already download it ? If yes is it possible to upload it somewhere else like mega ?
Thank you in advance
I'm running the 23/3 version of Mokee 5.02 as of a few hours. So far so good!
Does dual sim works well?
And battery consumption is similar to 4.4.4 RC7?
Did you detected any bugs?
Is it stable enough for a daily device?
Lord_Snake said:
Does dual sim works well?
And battery consumption is similar to 4.4.4 RC7?
Did you detected any bugs?
Is it stable enough for a daily device?
Click to expand...
Click to collapse
I'm using the previous version (1st march) and I used it daily
i don't use 2 sim cards.
I had 1 reboot (not a wished, it was because of a crash) in nearly one month
Lord_Snake said:
Does dual sim works well?
And battery consumption is similar to 4.4.4 RC7?
Did you detected any bugs?
Is it stable enough for a daily device?
Click to expand...
Click to collapse
The previous version dual SIM worked very well. I'll know if the dual SIM will work well for the new version later this week as I will be travelling.
Yes I'm using it for a daily work phone as I rely on it. Thou I have my ultra-stable iPhone 6 as my personal phone/backup :victory:
can someome upload it ?
EDIT: Someone post a mirror in other topic
I used this one : http://www.gamefront.com/files/24894999/MK50.2-nx507j-201503230233-UNOFFICIAL.zip
I think I get more spontaneous reboots with this new version than with the last version. However, it could be due to the memory leak issue all Android Lollipop phones have and isn't fixed until 5.1
Hoping to see Mokee 5.02 upgrade soon to 5.1 and integrate native dual SIM support...
Hello, I like the mokee rom,
If you have the file MK50.2 or more, please post it !
sdchew said:
I think I get more spontaneous reboots with this new version than with the last version. However, it could be due to the memory leak issue all Android Lollipop phones have and isn't fixed until 5.1
Hoping to see Mokee 5.02 upgrade soon to 5.1 and integrate native dual SIM support...
Click to expand...
Click to collapse
This has been confirmed in several posts on some of the Chinese bbs. Apparently, someone has released a temporary fix; although, I haven't tried it yet. I agree, I'm having the same problem. Additionally, it vibrates for everything. I currently have it set to vibrate only on phone and SMS, yet it does for everything and I cannot find out how to make it stop.
pedrud said:
This has been confirmed in several posts on some of the Chinese bbs. Apparently, someone has released a temporary fix; although, I haven't tried it yet. I agree, I'm having the same problem. Additionally, it vibrates for everything. I currently have it set to vibrate only on phone and SMS, yet it does for everything and I cannot find out how to make it stop.
Click to expand...
Click to collapse
I didn't noticed this kind of error
but I admit this is because of my config => my phone does not vibrate and it is my xiaomi MiBand who vibrate for specific notifications
does anybody have a custom recovery that works with android 5.0 on z7 mini.
I have stock 5.0 installed and wanted to flash the newest mokee. but when i want to make a backup through the old mokee cwm, but it always says "cant mount data".I would thing thats because of the changed partitions.
Anyway, is there any (non-chinese) recovery that i can use with stock 5.0?
sancho777 said:
does anybody have a custom recovery that works with android 5.0 on z7 mini.
I have stock 5.0 installed and wanted to flash the newest mokee. but when i want to make a backup through the old mokee cwm, but it always says "cant mount data".I would thing thats because of the changed partitions.
Anyway, is there any (non-chinese) recovery that i can use with stock 5.0?
Click to expand...
Click to collapse
Here in the z7 mini rom thread on post 781 (top) is a link to TWRP 2.8.5.0. However, I don't know if the new mokee works after flashing the nubia version of 5.0 because I don't think (someone can correct me) the mokee uses unified storage yet. Can someone verify this?
Thanks, trying TWRP right now.
So anybody knows if i can flash Mokee 5.02 after flashing Offical 5.0 with the new kind of partitions?
pedrud said:
Here in the z7 mini rom thread on post 781 (top) is a link to TWRP 2.8.5.0. However, I don't know if the new mokee works after flashing the nubia version of 5.0 because I don't think (someone can correct me) the mokee uses unified storage yet. Can someone verify this?
Click to expand...
Click to collapse
sancho777 said:
Thanks, trying TWRP right now.
So anybody knows if i can flash Mokee 5.02 after flashing Offical 5.0 with the new kind of partitions?
Click to expand...
Click to collapse
I did not tried it right now as i'm still discoverng this android 5 by nubia...
i just tried it 1 min and can already say that I may switch to mokee soon (I'll try the nubia rom 1 week I guess..)
the UI feels slow
I don't like the nubia theme
and beside of that, the French translation f(cuoco92 rom) is partial and canadian only (other timezone, other clock format, other keyboard layout...)
nubia's rom seems more unstable than mokee (from the first comments I read on cuoco92 facebook page)
it is also very BIG (double the size...)
If you are afraid of bricking the phone, you can also use the stupid chinese tool to install again kitkat on the phone, then install again mokee
but i guess (not sure !!!! ) that it should be possible to install mokee without doing this pain in the ass trick :/
sancho777 said:
Thanks, trying TWRP right now.
So anybody knows if i can flash Mokee 5.02 after flashing Offical 5.0 with the new kind of partitions?
Click to expand...
Click to collapse
No, you cannot. See this thread on the Nubia forum. CM12 and Mokee are still technically considered 4.4 because they do not use the unified storage. You will most likely brick the phone if you attempt to flash it. You have to first use the Nubia updater to go back to at least 1.82, then you can use CM12 or Mokee.
Hi guys! I've just cooked my first custom ROM for my Estar Takee 1 (octacore chinese smartphone with mediatek mt6592 CPU 2ghz)
I used dsixda kitchen on Linux and a stock JellyBean ROM as base.
I tryed to flash the .zip file from my custom recovery (TWRP) but I have this error
Code:
error executing updater binary in zip
What could be the problem ?
Another developer used the same stock ROM as base to make his own custom ROM (I'm using that one and it works!)
Maybe I have to use another kitchen?
You have more experience than me so I wait your replies. Thanks in advance
Somewhere on Xda i read that people solved this problem replacing the "updater binary" file inside the custom rom from another one taken from the stock rom...
I tryed to replace my updater binary with the one contained in a custom rom that works on my device but I can't still flash the zip!!
The new updater binary also shows this warning:
Code:
format() expects 5 args, got 2
Have you figured out the solution for this problem already? I am very interested in your work!
Sent from my takee 1 using XDA Labs
Oops duplicate
---------- Post added at 04:43 PM ---------- Previous post was at 04:21 PM ----------
Mich-C said:
Hi guys! I just cooked my first custom ROM for my Estar Takee 1 (octacore chinese smartphone with mediatek mt6592 CPU 2ghz)
I used dsixda kitchen on Linux and a stock JellyBean ROM as base.
I tryed to flash the .zip file from my custom recovery (TWRP) but I have this error
What could be the problem ?
Another developer used the same stock ROM as base to make his own custom ROM (I'm using that one and it works!)
Maybe I have to use another kitchen?
You have more experience than me so I wait your replies. Thanks in advance
Click to expand...
Click to collapse
@[email protected] can you help @Mich-C solve this TWRP bug in a new custom ROM for Takee 1, please?
Sent from my takee 1 using XDA Labs
Could you post your updater-binary and updater-script file here
Hi @YuriRM many thanks for interesting in the project. Thanks also to you @[email protected]
Here are the updater-binary and updater script from my custom romhttps://drive.google.com/open?id=1_xCsP_GqGUj202jdx4xOgXwPSwDprEam.
I used a Takee1 stock rom as base to develop this rom but I used a stock rom downloaded from internet because I lost the backup of my original stock rom.
We can also try to make a new rom from YOUR stock rom if you can provide it to me
Long time ago I read somewhere that the Takee1 was sold in 2 versions with a small difference, I have to check better this thing
List of stock and custom ROMs for Takee 1
Mich-C said:
Hi @YuriRM many thanks for interesting in the project. Thanks also to you @[email protected]
Here are the updater-binary and updater script from my custom romhttps://drive.google.com/open?id=1_xCsP_GqGUj202jdx4xOgXwPSwDprEam.
I used a Takee1 stock rom as base to develop this rom but I used a stock rom downloaded from internet because I lost the backup of my original stock rom.
We can also try to make a new rom from YOUR stock rom if you can provide it to me
Long time ago I read somewhere that the Takee1 was sold in 2 versions with a small difference, I have to check better this thing
Click to expand...
Click to collapse
Stock ROMs and custom ROMs for TAKEE 1
https://forum.xda-developers.com/showpost.php?p=73882980&postcount=1134
Android 4.2.2 - Stock firmware of September 2015
Android 4.2.2 - Stock firmware of October 2015
Android 4.2.2 - Stock firmware of November 2015
Android 4.2.2 - Patched stock firmware of November 2015 with boot image of October 2015
Android 4.4.2 - Third-party ROM by LuckAsFB, (Release date: 26th December 2016)
Android 6.0.1 - Third-party ROM by VladJocker (Release date: 18th November 2016)
Android 7.1.2 - Third-party ROM by Francesinha (in development)
Sent from my takee 1 using XDA Labs
Mich-C said:
Hi @YuriRM many thanks for interesting in the project. Thanks also to you @[email protected]
Here are the updater-binary and updater script from my custom romhttps://drive.google.com/open?id=1_xCsP_GqGUj202jdx4xOgXwPSwDprEam.
I used a Takee1 stock rom as base to develop this rom but I used a stock rom downloaded from internet because I lost the backup of my original stock rom.
We can also try to make a new rom from YOUR stock rom if you can provide it to me
Long time ago I read somewhere that the Takee1 was sold in 2 versions with a small difference, I have to check better this thing
Click to expand...
Click to collapse
Your Script looks fine, may be problem lies in your updater-binary file try using this attached update binary file. https://drive.google.com/file/d/1UZImzerlBglJWFDrPdvok-X7YBsl5sUQ/view?usp=drivesdk
Edit: Also with what kind of editor you used to edit updater script. If you used default notepad app then its obvious you have lost your encoding. Its important that you should use notepad ++
@Mich-C
Francesinha is porting Android 7.1.2 from Validus OS to TAKEE 1. He does not have this device. He ported Mokee 7.1.2 to BQ Aquaris E5 FHD (MT6592).
I have prepared detailed instructions for Francesinha on this post. It is a Portuguese and English mix. This text is the best instruction set for TAKEE 1 ROMs yet. Would you like to read a fully English version? It can be produced by me if you request it.
Are you willing to test this Android 7.1.2 ROM by Francesinha once it is ready for download?
https://www.androidpt.com/topic/64707-romportmokee712-mokee-para-o-bq-aquaris-e5-fhd/#entry636634
Sent from my takee 1 using XDA Labs
[email protected] said:
Your Script looks fine, may be problem lies in your updater-binary file try using this attached update binary file. https://drive.google.com/file/d/1UZImzerlBglJWFDrPdvok-X7YBsl5sUQ/view?usp=drivesdk
Edit: Also with what kind of editor you used to edit updater script. If you used default notepad app then its obvious you have lost your encoding. Its important that you should use notepad ++
Click to expand...
Click to collapse
Wow! In the next days I'll replace the updater-script in my rom and I'll report back the result.
It seems to me that I didn't edit at all those 2 files, they were just generated by the dsixda kitchen, anyway I usually use the leafpad editor installed on my linux distro
YuriRM said:
Stock ROMs and custom ROMs for TAKEE 1
https://forum.xda-developers.com/showpost.php?p=73882980&postcount=1134
Sent from my takee 1 using XDA Labs
Click to expand...
Click to collapse
Never found this post on xda!
I installed that Kitkat Rom 4.4.2 linked in the post(developed by a russian dev called luckasfb) it worked perfectly except for the main camera (completely unusable for a driver problem)
Then I went back to another Stock rom found on NeedRom but the O.S. is unstable and the microphone doesn't work if the screen it's locked.
I need to test those other 2 stock roms!
Anyway, did you tryed that 6.0.1 rom linked in the post?
Mich-C said:
Never found this post on xda!
I installed the Kitkat Rom 4.4.2. developed by a russian dev called luckasfb and it worked perfectly except for the main camera (completely unusable, it is a driver problem)
Then I went back to another Stock rom found on NeedRom but the O.S. is unstable and the microphone doesn't work if the screen it's loked.
I need to test those other 2 stock roms!
Anyway, did you tryed the 6.0.1 rom linked in the post?
Click to expand...
Click to collapse
The official tester for TAKEE 1 ROMs is @io2345. He has produced excellent test reports and short guides on LuckasFB and VladJocker ROMs. Follow his instructions to achieve fully working cameras on Android 4.4 and 6.0.1 ROMs. @io2345 is the best tester of all TAKEE 1 owners! Io2345 and I have a very productive partnership.
We should be having this conversation in the TAKEE 1 thread on order to benefit all owners.
Sent from my takee 1 using XDA Labs
YuriRM said:
@Mich-C
Francesinha is porting Android 7.1.2 from Validus OS to TAKEE 1. He does not have this device. He ported Mokee 7.1.2 to BQ Aquaris E5 FHD (MT6592).
I have prepared detailed instructions for Francesinha on this post. It is a Portuguese and English mix. This text is the best instruction set for TAKEE 1 ROMs yet. Would you like to read a fully English version? It can be produced by me if you request it.
Are you willing to test this Android 7.1.2 ROM by Francesinha once it is ready for download?
https://www.androidpt.com/topic/64707-romportmokee712-mokee-para-o-bq-aquaris-e5-fhd/#entry636634
Sent from my takee 1 using XDA Labs
Click to expand...
Click to collapse
So from what I understood Francesinha can't speak english but you portuguese and so can help us to communicate?
I'm italian so I understand spanish and french quite well but with portuguese it's different so yes, I need help XD
Anyway once the Rom is ready why don't you test it too? It should be just a zip file as usual
Mich-C said:
So from what I understood Francesinha can't speak english but you portuguese and so can help us to communicate?
I'm italian so I understand spanish and french quite well but with portuguese it's different so yes, I need help XD
Anyway once the Rom is ready why don't you test it too? It should be just a zip file as usual
Click to expand...
Click to collapse
AVAST antivirus has disabled KingRoot and removed several components in my Takee 1 device. Therefore, I lost root access and the ability to install new ROMs in this device. But I am quite happy with the 3D performance of the 10th September 2015 stock ROM. Unfortunately, it has Gyroscope and GPS bugs.
Another TAKEE 1 unit that I owned and now belongs to my cousin has the patched stock ROM of November 2015 with boot image of October 2015. It is working nice!
I will do the translation in order to be read by everybody.
P.S. - Francesinha is a 16 year old boy. He understands English with Google Translator, I guess. He will be pleased to read your post in his thread. You are welcomed in AndroidPT too!
Sent from my takee 1 using XDA Labs
YuriRM said:
AVAST antivirus has disabled KingRoot and removed several components in my Takee 1 device. Therefore, I lost root access and the ability to install new ROMs in this device. But I am quite happy with the 3D performance of the 10th September 2015 stock ROM. Unfortunately, it has Gyroscope and GPS bugs.
Another TAKEE 1 unit that I owned and now belongs to my cousin has the patched stock ROM of November 2015 with boot image of October 2015. It is working nice!
I will do the translation in order to be read by everybody.
P.S. - Francesinha is a 16 year old boy. He understands English with Google Translator, I guess. He will be pleased to read your post in his thread. You are welcomed in AndroidPT too!
Sent from my takee 1 using XDA Labs
Click to expand...
Click to collapse
Woah! Avast done this when you plugged in the phone to the PC?!
Did you try to flash a stock from the PC using SP flash tool? It worked for me even when the phone was bricked. Flashing a zip from the sd-card always has a lower succes rate.
Let's hope well for Francesinha work! If he sign in on Xda we can help him better
How to install a bug free Android 4.4 custom ROM by LuckasFB (Written by @io2345)
How to install a bug free Android 4.4 custom ROM by LuckasFB.
Written by @io2345
After getting some experience with the latest KitKat-ROM (4.4.2) developed by LuckasFB, I can tell you all that it's useable. VoIP calls work as well as GPS, Gyro, 3D. Not sure if LuckasFB is still working on better/newer firmware, so currently it is probably the best choice. All of the hints and links are posted "somewhere" in this thread with more than 100 pages and over 1000 entries, so let me sum it up (YuriRM already did that several times before):
First, install TRWP recovery: Flash the file inside this archive (you have to extract it)
https://mega.nz/#!hgYCwIYb!BYlmRnTVzWribPKlQDkmCR5ggT5GCkflIFbjeawg5Jk
as recovery-file using SPFlash-Tool.
Place this two files (without extracting them) in the phones memory or the root of your phones SD-Card (if you use one):
KK custom ROM
https://mega.nz/#!B5Q3gAga!OLh4sLFZ8dxkzkwazV1hI9xfIc2rP2a_C4QL_LQlOGA
micro.zip
https://mega.nz/#!o5RE3KYb!Wel6c3q8GKEovptvRdAZFj1ZlCERiCWYsjjj8K1_bg0
Connect phone to a charger, switch it off, and when restarting it, hold "Vol up" pressed, until TRWP-Menu shows. Use "Wipe"-Function, after that "Install" and select the two ZIP-Files, install them and reboot.
Install from play store any power manager app that can do a "hot reboot" (example: "Power Manager" by Guiseppe Montuoro).
After boot wait some time (like 10 minutes), then try to open camera. When the selfie camera is started, make a hot reboot using the power manager app. Start camera again, both cameras will work now (note: as long as "unable to open camera" or "gallery error" shows up or camera just doesn't start, hot reboot is useless).
Getting 3D-Effect (only necessary if you use SD-Card): Copy the two files "HolographyProfile" and "matrix" from the phones folder "Android" into the folder "Android" on the sd-card. The (already preinstalled) App "3D Video" contains four 3D Movies. Hint: If 3D-Effect is ghosty (doubled elements in the picture) try to tilt the phone just a few degrees to the right instead of looking in the very middle of the screen.
Rather than switching off the phone at night, only put it in airplane mode. Saves energy for the battery and you from doing a camera restart the next day...
App that makes use of the gyro effect and has appropriate videos: Install DiscoveryVR from play store. Open a video (like: Shark Storm), move the phone up/down/left/right to change the viewing angle.
https://forum.xda-developers.com/showpost.php?p=73634579&postcount=1127
Besides from saying, that leaving the screen on when charging is no option for me, I am quite pleased with the current firmware (don't have any clicks either). I told you, that I do not switch off the phone but put it into airplane at night, where battery drops by 1% or even stays at the same value until the morning. Once I had an issue with the card in SIM1 not willing to work when leaving airplane mode, but that occured only once in ten days now and can be solved by a normal reboot. Battery of the phone isn't too strong, but takes me through the day with normal usage of a man (really doubt, if a woman can do one day without recharging). Usually I end up at night with about 30% left. Screen is the greatest consumer, so if you watch a movie on the phone, you will have a drop of 10% of the battery every 15-20 minutes. WiFi and mobile radio also consume some greater part of the energy, so you might do a good while longer if you watch movies in airplane mode. WiFi reception and GPS are just so-so, maybe due to the metal frame of the Takee. For me it is good enough, and I just love the smooth finish of the phone.
https://forum.xda-developers.com/showpost.php?p=73766188&postcount=1131
Hi @YuriRM new updates on my custom stock rom for the takee1:
I just replaced in my .zip rom the update-binary file kindly provided by @[email protected]
But I couldn't test this "fixed" rom : I tryed to boot my phone into recovery mode as usual (power button + volume down) but strangely it didn't work so I had to dowload an app that allowed me to reboot into recovery mode.
Well, I just got a message that says there isn't a recovery on my phone ( the phone can boot the OS without issues)
I don't know how it could be possible, I flashed and fixed phones with bricked roms many times but I have never got a problem like this...
What can you can tell me about?
Mich-C said:
Hi @YuriRM new updates on my custom stock rom for the takee1:
I just replaced in my .zip rom the update-binary file kindly provided by @[email protected]
But I couldn't test this "fixed" rom : I tryed to boot my phone into recovery mode as usual (power button + volume down) but strangely it didn't work so I had to dowload an app that allowed me to reboot into recovery mode.
Well, I just got a message that says there isn't a recovery on my phone ( the phone can boot the OS without issues)
I don't know how it could be possible, I flashed and fixed phones with bricked roms many times but I have never got a problem like this...
What can you can tell me about?
Click to expand...
Click to collapse
Hi Mich-C! I am on vacations now. Maybe @[email protected] can help you.
My phone has gone bezerk after using the charger from another phone. It often freezes and the screen goes Black. I may try to reinstall Android.
If something is damaged then I will buy another 3D phone... the SuperD D1 from eFox or CooliCool.
Sent from my takee 1 using XDA Labs
YuriRM said:
Hi Mich-C! I am on vacations now. Maybe @[email protected] can help you.
My phone has gone bezerk after using the charger from another phone. It often freezes and the screen goes Black. I may try to reinstall Android.
If something is damaged then I will buy another 3D phone... the SuperD D1 from eFox or CooliCool.
Click to expand...
Click to collapse
Yes, try to reinstall the stock rom and buy a new battery I think you' ll solve the problem.
About my device instead: We have many roms for the takee1 and I made my own rom too but If I can't access recovery how can I flash them?!
Ok I' ll wait your return from vacation
You can use SPFlash and only flash the recovery.img, can't you? Use the LuckasFB Recovery-Image containing TWRP28.
BTW: You know that for Takee you can only access Recovery if the phone is connected to a charger - do you?