CLOUDFONE EXCITE 501D CUSTOM ROM
Android Jellybean [4.1.2]
- Pre-rooted
- 60 Framerate per second
- Good for gamers
- Smooth UI
- Full S4 UI
- S4 Launcher
- S4 Weather Widget
- S4 Status Bar
- S4 Font ( Rosemary )
- JMP TWEAKS
- SECRET RECIPE FOR GAMERS
- Very Smooth on lite games like (temple run, angry birds, fruit ninja, plants vs zombies 2, etc)
NEW TO VERSION 2.9:
- INIT.D SUPPORT
- REMOVE THOSE USELESS WEATHER APP AND WIDGETS
- REMOVE USELESS LIVE WALLPAPER
- DEBLOATED
- ZIPALIGNED
- BUILT-IN VIPER4ANDROID
-ADDED X-REALITY ENGINE
-ADDED NEW PATCH
-ADDED ALBUM AND PHOTO EDITOR IN ORDER TO CHANGE LOCKSCREEN WALLPAPER
-IMPROVE GPS LOCKTIME
-LESSER FC'S ON SOME HEAVY APPS AND GAMES
-MORE STABLE
-ADDED XPOSED INSTALLER
-ADDED BUILD.PROP TWEAKS
XDA:DevDB Information
Kalawakan v2.9, ROM for all devices (see above for details)
Contributors
flarestar123, Leingod0923
ROM OS Version: 4.1.x Jelly Bean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 4.1.1-4.1.2
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 2.9
Stable Release Date: 2014-11-01
Created 2014-10-31
Last Updated 2014-11-04
CREDITS:
http://forum.xda-developers.com/showthread.php?t=2025391 @jigarmpattani
Thank him for I use his ROM from the very base
http://forum.xda-developers.com/showthread.php?t=2191223 @zhuhang
Thank him for his amazing viper4android
Rymoj Serolf
Ronald Hipz Pajal
Jaymar Dela Cruz
Yconne Libot
Shine Lee
Charliemae de Castro
Andre Aggasid
MyPhone A848i Family
Chinese Developers
Myphone PH Developers *OFFICIAL AND UNOFFICIAL DEVS*
Micromax XDA Developers
PROCEDURE TO FLASH THE ROM
1. WIPE DATA
2. WIPE CACHE PARTITION
3. WIPE DALVIK CACHE IN ADVANCE
4. GO TO MOUNT AND STORAGE AND FORMAT SYSTEM
5. INSTALL ZIP FROM SD CARD
6. REBOOT SYSTEM NOW
7. FINISH THE SET UP
8. OPEN VIPER4ANDROID AND INSTALL ITS DRIVER
9. OPEN XPOSED AND INSTALL ITS FRAMEWORK
10. REBOOT
FOR FLASHING THE PATCH
1. PLACE THE PATCH TO SD CARD
2. INSTALL THE ZIP FROM SD CARD
3. REBOOT SYSTEM NOW
SCREENSHOTS: https://www.facebook.com/media/set/?set=oa.517481885003841&type=1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DON'T BE A SILENT DOWNLOADER HIT THANKS IF YOU LIKED MY WORK :good:DOWNLOAD LINK:ROM LINK: http://www.mediafire.com/download/d45gacsl1w3eb1c/Kalawakan_Rom_v2.9.zip
NEW! PATCH LINK: http://d-h.st/FIR
NOTE: IF YOU WANT TO PORT TO ANOTHER DEVICE PLEASE ASK PERMISSION
Re-partitioning and add on section
CLOUDFONE 501D REPARTION
Procedure:
BACKUP! BACKUP! BACKUP!
1. Go to CWM/TWRP Recovery
2. Install zip from sdcard >> then choose zip from sdcard
3. Flash "desired repartition" when it's complete
4. Choose "go back" then "wipe data/factory reset, wipe cache and in advanced wipe dalvik cache"
5. Flash again "desired repartition"
6. Go back >> go to advanced >> reboot to recovery
7. Wipe data/ factory reset and wipe cache
8. Flash your "DESIRED ROM" and then reboot
***I do not own this work, this is just a repost***
Credits to: Archie Shinshan
Steven Sombremesana
DOWNLOAD LINK:
2.5gb internal and 55mb
DIRECT LINK: http://www.4shared.com/zip/OC0trpH5/A919_Data_Repartition_25GB_int.html
MIRROR LINK: https://docs.google.com/file/d/0BwE0fpvujMnSRUdxY1huellQM28/edit?pli=1
1.5gb internal and 1gb sd card
DIRECT LINK: http://www.4shared.com/zip/a0IE1Fxc/A919_Data_Repartition_15gb_int.html
Finished uploading
download links are now available enjoy!
The CWM mod for my 501D does not seem to work as rebooting into recovery mode freezes the phone into the "cloudfone" booting image. And it also does the same thing when I try to boot into recovery mode. Is there a way to flash your custom rom to the phone with the use of a software? Thanks.
lhites said:
The CWM mod for my 501D does not seem to work as rebooting into recovery mode freezes the phone into the "cloudfone" booting image. And it also does the same thing when I try to boot into recovery mode. Is there a way to flash your custom rom to the phone with the use of a software? Thanks.
Click to expand...
Click to collapse
Please repeat the steps here in installing CWM in our phones: http://www.symbianize.com/showthread.php?t=1136946
Because it is better to have a CWM working so that you can also flash my repartition tutorials.
flarestar123 said:
Please repeat the steps here in installing CWM in our phones: http://www.symbianize.com/showthread.php?t=1136946
Because it is better to have a CWM working so that you can also flash my repartition tutorials.
Click to expand...
Click to collapse
I am sorry. But I already did follow the thread you were referring to before I requested/posted for some help. I have read about Flashify, can I use it instead to flash your custom rom? (http://forum.xda-developers.com/showthread.php?t=2798257) Or can I go ahead with Magic TWRP rather than CWM (since it does not work on mine). And then just use Magic TWRP to flash your custom rom? Agyamanak
lhites said:
I am sorry. But I already did follow the thread you were referring to before I requested/posted for some help.
I have read about Flashify, can I use it instead to flash your custom rom? (http://forum.xda-developers.com/showthread.php?t=2798257)
Agyaman
Click to expand...
Click to collapse
I really recommend you use carliv or cwm recovery because if something goes wrong you can still recover your bricked phone. But if you use flashify then you got an error while flashing the rom. Then dont blame me if you brick your phone thus you cant anymore flash a stock rom to repair it cause you dont have a working CWM. If I have the ability to install a cwm in my phone so you can cause we have the same phone.
flarestar123 said:
I really recommend you use carliv or cwm recovery because if something goes wrong you can still recover your bricked phone. But if you use flashify then you got an error while flashing the rom. Then dont blame me if you brick your phone thus you cant anymore flash a stock rom to repair it cause you dont have a working CWM. If I have the ability to install a cwm in my phone so you can cause we have the same phone.
Click to expand...
Click to collapse
Thank you. I know I can't just blame anyone except myself if I brick my 501D phone. That much I already know. But your suggestion did not work on my android phone (since I already went through it many times without success). Have you tried Magic TWRP? Or some other way of having a custom recovery? If not, then all I can do is be patient with my buggy phone
lhites said:
Thank you. I know I can't just blame anyone except myself if I brick my 501D phone. That much I already know. But your suggestion did not work on my android phone (since I already went through it many times without success). Have you tried Magic TWRP? Or some other way of having a custom recovery? If not, then all I can do is be patient with my buggy phone
Click to expand...
Click to collapse
You can follow an alternative step in installing CWM recovery on our phone: http://forum.xda-developers.com/showthread.php?t=2519432
Okay thanks. Will try this and let you know how it goes. Wish me luck
Good news! Flashify was able to successfully flash CWM Having gone into CWM recovery mode, CWM reported a "bad" rom while attempting to flash your custom rom. Will download another copy of your rom when I am on a faster connection. Thank you for all your help.
lhites said:
Good news! Flashify was able to successfully flash CWM Having gone into CWM recovery mode, CWM reported a "bad" rom while attempting to flash your custom rom. Will download another copy of your rom when I am on a faster connection. Thank you for all your help.
Click to expand...
Click to collapse
Okay thats great because I am planning to upload a new custom rom for our phone.
Then I'll wait for your new custom rom just flashed the deodexed stock rom two days ago, will use it for the meantime.
I was able to flash the kalawakan rom unfortunately I did not like it. So I went back to the stock deodexed rom. flashing the backup via cwm did not work either. I had to flash the rom from start. FYI.
My cloudfone 501D shuts off intermittently without any warning. I thought that reflashing will solve the problem. Do you have any ideas on how to solve this problem? Thanks in advance.
nice
nice
Ask lng po .
Pwede po bang iflash na yan kahit naka kalawakan rom v2 lng po ako? o kailngan pang ibalik sastockrom ng cloudfone 501d ?
erisjean said:
Pwede po bang iflash na yan kahit naka kalawakan rom v2 lng po ako? o kailngan pang ibalik sastockrom ng cloudfone 501d ?
Click to expand...
Click to collapse
Just do the proper wiping to avoid any conflicts and YES you can flash it eventhough you are already at Kalawakan Rom v2
Siong05 said:
nice
Click to expand...
Click to collapse
It would be nicer if you can wait for the lollipop theme rom
lhites said:
My cloudfone 501D shuts off intermittently without any warning. I thought that reflashing will solve the problem. Do you have any ideas on how to solve this problem? Thanks in advance.
Click to expand...
Click to collapse
Please wait for the new rom maybe this will help you solve the problem
Related
Hello, Infusers...im back and ive brought with me TeamWin Recovery Project! Official TWRP website: http://www.teamw.in/project/twrp2
What is this?
-Its an alternitive to CWM recovery
What are the advantages?
-Full touch screen interface
-Built in file manager
-keyboard (gives you the ability to name your backups...or rename other files from with in recovery)
-clock
-battery percentage
-swipe to confirm flashes/wipes (no more of the "no no no no yes no no"
-themeable!!!
-and more!!!
***DOES NOT WORK WITH MTD JELLYBEAN...yet***
Unfortunatly our recovery is built into the boot.img after flashing any ics rom you will lose the twrp recovery and get cwm recovery again...just tick the box to re-inject twrp before sliding to confirm your flash...or go to advance options and click on re-inject twrp
Download:
TWRP
Flashing Instructions (does not effect your current set up/kernel...only replaces CWM)
1) boot into recovery
2) flash zip
3) reboot
4) next time you go to recovery you will have TWRP
5) Flash this zip after every new rom flash to keep TWRP
***important for updating***
-if updating twrp from a previous build make sure you disable "re-inject twrp after flash" if you dont it will reinject the old twrp
-If coming from gingerbread you have to boot into your ics or jb Rom before being able to flash the zip...after that you can flash after every Rom flash
how does the zip work? i thought it was built into the boot.img?
Credit goes to smasher816 for this..he made an install script that takes your boot.img of your rom, then takes the recovery ( ramdisk-recovery.img) and injects it into your current boot.img...leaving the actual kernel untouched!
Satandard Disclaimer
Use this recovery at your own risk!!! im not responsible for anything that happens to you, your phone, your friends, your family, or anything but i will do my best to resolve any and all problems you may encounter
Thanks/Credit:
TeamWin-Recovery/source/compiling instructions
Entropy-CM9/kernel/guide for compiling/source
JT-for getting us ics in the first place
JScott30-sold me his infuse which allowed for me to do this
Smasher816-your install script has allowed for an easy recovery flash
Did i miss anyone? -let me know...dont want to leave any one out
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the above screen shots were taking from http://www.teamw.in/project/twrp2
the below screenshots are pictures taken of my infuse with it in action
And...video of it in action
http://www.youtube.com/watch?v=7gJ7idj8y0g&feature=plcp
TWRP-2.2.1.4 8-6-12
-fixed aroma
-should be completly bug free
TWRP 2.2.1 6-8-12
-updated to twrp 2.2.1.4
-fixed backups
TWRP 2.2.1 8-3-12
-Added the abilty to reinject twrp through an option under the advanced menu...use that option or reflash zip
TWRP 2.2.1 sdfix
-Fixed sdcard error
-fixed install script so you no longer have to mount system in mounts instorage...just flash the zip and it will mount for you
8-2-12
-initial release
Things to do...
1) Figure out if its possible to compile the recovery and flash it with out messing with a user's kernel/current set up
-solved...op has been updated with fix
2) fix the sdcard error
-solved...op has been updated with fix
3) fix backup problem (cant create a backup)...currently the only known bug
-solved fix uploaded to goo.im
4) make a CWM recovery zip for people who want to go back to CWM
-done, added as an atachment to the op
5) fix the aroma bug...
-fixed...uploaded to goo.im
6) Keep this up to date with official twrp source
-on going process...ill check every other day for updates to the source
TWRP THEMES
You can find some themes for twrp here: TWRP 2.X Themes
-keep in mind that themes can introduce bugs...so use them at your own risk...if your intrested in creating your own them check out this: http://teamw.in/project/twrp2themers
-themes must go in this directory /sdcard/TWRP/theme/ and it must be named ui.zip -reboot to recovery and it will be applied...thats right just reboot no need to flash!
My TWRP Themes -hosted on goo.im (soon to be featuring every color of the rainbow...and then some)
Inverted theme! by supernewbdev
First....
Very nice bro..this is awesome no more vol up+down button and power when flashing roms when your are in recovery mode and all fully touch screen...good job sir
Nice man always great to have options!
Sent from my SGH-I997 using xda app-developers app
I have been wanting to try twrp in my infuse since I tried it on my transformer.
This is a great addition to our community, Thanks for bringing it! :victory:
Edit: I presume it still not compatible with JB, am i right?
andros11 said:
I have been wanting to try twrp in my infuse since I tried it on my transformer.
This is a great addition to our community, Thanks for bringing it! :victory:
Edit: I presume it still not compatible with JB, am i right?
Click to expand...
Click to collapse
At the moment no...its built into the ics boot.img -so flashing this would give you an ics kernel
Not sure when and if ill be able to bring it to JB...will have to wait for TeamWin to update it for JB
EDIT: i think i know how to let people use this without messing with there current kernel/set up...gotta test the theory first
Edit #2...theory correct...no more will you have to flash the boot.img or CM9 to get TWRP...OP will be updated shortly with details
Omg. Mg this is awesome downloading as of now
Edit: can the boot.img be flashed with sgs kernel flasher?
Edit#2: saw the zip flashed it and it works like a charm.
Sent from my AOKP'd Infuse 4G
OP updated...just download the zip and flash it-next time you boot to recovery you will have TWRP...just make sure you mount system before flashing...
EDIT: if my other theory is correct...this may now be compatible with JB...gonna download cm10 now and test the zip with it...will report back later
isaiahe97 said:
Omg. Mg this is awesome downloading as of now
Edit: can the boot.img be flashed with sgs kernel flasher?
Sent from my AOKP'd Infuse 4G
Click to expand...
Click to collapse
not sure...but you can download the zip and flash that instead in recovery...it will not mess with your rom or kernel
works with jellybean...just mount system and flash the zip...
Recovery updated...fixed the sdcard error, as well as edited the updater script to mount system...in other words you dont have to mount system in "mounts and storage" anymore just download and flash
currently only known bug at the moment is not being able to create a backup...im looking into it
EDIT: Just found out there's a way to enable the recovery to auto insert itself after every Rom flash...currently working on it...if it works then one flash and you will have it for good! It will be added to the advanced settings I believe...so you can enable the auto insert or disable it if you wanna go back to old cwm...
EDIT 2: alright...misread...it doesnt auto insert :/ but still useful tho heres what it does: after flashing a rom instead of flashing the recovery zip again you go to advanced options, in there on the bottom right corner you will see the option to "re-inject TWRP" it essentially does the same thing as the zip...so if you delete the zip or dont wanna flash the recovery zip ever again just use that option after every rom fash and it will inject the recovery into the rom
ill include the re-inject option in the next update (when i figure out and fix the backup problem...) unless you guys want that now...just dont wanna do a bunch of tiny updates in one day lol...i feel like that would be annoying for you guys
Been getting tired of CWM so i am gonna have to try this out. Thks:cyclops::good:
BTW. Doesn't the face plate on the Otterbox case mess with infared sensor in detecting during calls.
I got a Ballastic case the other day and i couldn't seem to hang up a damn phone call after rebooting
---------- Post added at 11:21 PM ---------- Previous post was at 11:09 PM ----------
mg2195 said:
OP updated...just download the zip and flash it-next time you boot to recovery you will have TWRP...just make sure you mount system before flashing...
EDIT: if my other theory is correct...this may now be compatible with JB...gonna download cm10 now and test the zip with it...will report back later
Click to expand...
Click to collapse
Might wanna edit the OP.....
1) boot into recovery
2) Mount system (mounts and storage > mount /system)
3) flash zip
4) reboot
5) next time you go to recovery you will have TWRP
6) Flash this zip after every new rom flash to keep TWRP
Click to expand...
Click to collapse
slicingtaco said:
Been getting tired of CWM so i am gonna have to try this out. Thks:cyclops::good:
BTW. Doesn't the face plate on the Otterbox case mess with infared sensor in detecting during calls.
I got a Ballastic case the other day and i couldn't seem to hang up a damn phone call after rebooting
---------- Post added at 11:21 PM ---------- Previous post was at 11:09 PM ----------
Might wanna edit the OP.....
Click to expand...
Click to collapse
I fixed it so that when you flash it you no longer need to mount system...if you have the twrp 2.2.1 sdfix then you no longer need to mount system (I added the command in the updater script to.mount it)
Sooooo...just download, flash and enjoy...
Anyways...two days of non stop compiling...and I'm only doing recovery...don't know how the guys (Scott) at the CM10 thread do it...I'm pooped, time for bed
Also I don't use my infuse as my DD...so I don't have a sim in it...I use it for development only...my vivid is my DD
Sent from my HTC Holiday using Tapatalk 2
first of all, coolioso ! second, thanks! third, ok so to make sure, do I flash a rom, then reboot into recovery, then flash this alter-recovery, or can I just flash it along with the rom and the gapps ect.?
I'm loving this MG, This looks and feel so good. Thanks
Sent from my SGH-I997 using Tapatalk 2
Excellent work. Thank you.
megazeroxuxm said:
first of all, coolioso ! second, thanks! third, ok so to make sure, do I flash a rom, then reboot into recovery, then flash this alter-recovery, or can I just flash it along with the rom and the gapps ect.?
Click to expand...
Click to collapse
You can flash this and reboot into recovery
You can flash it after a Rom flash
You can flash it anytime...but if you flash a Rom make sure you flash this again
Sent from my HTC Holiday using Tapatalk 2
Back up will be great. I know you are working on that issue.
Also, will this only work with the Samsung Infuse 4G.
Hi Gionee E3 owners,
I finished porting CWM 6.0.2.8 to our device. Tested it myself and released after ensuring its working fine.
Now you can enjoy newer CWM 6.0.3.3, which is highest CWM available for our device
ROOTING INSTRUCTIONS:
1. Download MTK ADB DRIVERS and install on your PC
2. Download Motochopper
3. Extract the entire contents of the zip file.
4. The Ensure USB Debugging mode is enabled on your device by going to Settings>Developer options>USB Debugging
5. Connect your device to your PC via USB.
6. Navigate to the Motochopper extracted directory and execute “run.bat”
7. Approve the ADB connection from your PC to your device.
Now you are rooted
You can also use MTK Droid tools to root your Phone
>>>>>>>>>>>>>>>>>>>>>DOWNLOADS<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
CWM 6.0.2.8
CWM 6.0.3.3
Calrliv_Touch_Recovery_2.2_CWM_6.0.4.4_For Gionee_E3_CN_Base : Please use this recovery on Chinese base only, as I am on Chinese base ROM now, I could only port it to Chine base.
Screen:
'
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
RECOVERY FLASHING INSTRUCTIONS
A word of caution, though there is no risk involved in flashing this CWM, as I have already tested it,remember are dealing with a System file and it can cause accidental software issues/ corruption. Therefore the warning is mandatory
WARNING: PLEASE DO NOT BLAME ME IF YOU BRICK YOUR PHONE. PLEASE PROCEED ONLY IF YOU KNOW HOW TO RESTORE YOUR PHONE BACK TO WORKING CONDITION.
NOTE: For recovery installation by this method Root access is mandatory
1. Download the recovery
2. Put it on root folder of internal memory
3. Download MobileUncle tool.apk and install it.
4. Open MobileUncle tool give root permission and
5. Select recovery.img option and chose the recovery.img file you placed on internal sdcard.
6. follow instructions and the mobile will boot into CWM.
7. You are done with CWM.
Want to revert to stock recovery download the stock recovery attached here and follow above method to flash.
CREDITS:
Rua1 for MTK Droid Root & Tools v2.4.8
Russian Master Shifu Michfood for his tool
C3C076 - for CWM 6.0.3.3 for porting
yuweng for his awesome guide CWM port
lopestom: for inspiring me and guiding me
shankhuaa: for his initial cwm release
Me for Porting it to Gionee E3
Please PM me if I have missed anyone to be mentioned in the list
_________________________________________________________________________________________
========================================================================================================================
XPERIA HD ROM for GIONEE ELIFE E3
I do not take any credit of creating this awesome ROM, It is completely developed by Kumar abhishek for Micromax A116. I just customized it for Gionee E3. So thank the developer for this ROM. You can thank me to make it easy for you to install and run it on our device.
>>>>>>>>>>>>>>>>>>>>>DOWNLOAD<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
XPERIA HDv1
Based on XperiaJelly powered by Kumar Abhishek
Features
Steps for installing ROM:
1.Please educate yourself first what is custom ROM and what are the consequences of installing custom ROM. If you feel Custom ROM is better than stock and don't blame anyone for your actions please proceed....
2. Download the ROM from above link
3. Root your stock ROM and install CWM recovery provided above.
4. Reboot into CWM and backup your ROM first.
5. Now put the downloaded ROM on root of your SDCARD.
6. Clear Cache, Dalvik Cache, Factory reset.
7. Go to Mounts and storage format /system
8. Now install zip from SDCARD and select the downloaded ROM from SDCARD.
9. Once install is complete reboot into system.
Now you can customize the ROM the way you want.
Please remember it contains xposed framework file to be installed and customize various components as per your needs.
========================================================================================================================
LENOVO SUPER CAMERA APP- The Best Camera application with bunch of features
Here is the Lenovo Super Camera that is very much compatible with Gionee E3. It is the best custom camera app I've seen for our devices and you will definitely love it.
THE PIP ONE OF THE FEATURES WHICH IS ACTUALLY PICTURE IN PICTURE LIKE GALAXY S4 CAMERA NOT AVAILABLE TO ANY OTHER DEVICE.
You can download the app from below links and install as a regular application
The Phone Calling Permissions is removed in v3.5.5.0128.130812.19126 to avoid any auto calling by app.
Download:
1. Lenovo Super Camera v3.5.5.0128.130812.19126.apk
2. Lenovo Super Camera v3.1.3.0313.130712.17796.apk
3. Lenovo Super Camera v3.1.2.apk
PS: The burst mode and a few effects gives FC's but the rest works fine.
Keep the camera resolution at the maximum and you will see that a few effects work. The camera is not in the maximum resolution by default.
Screens:
Phone Calling permissions removed.
Please thank a2441918 for bringing this camera to all the devices. Please follow the link for any other detail.
========================================================================================================
Awesome man!! :d
Thanks
Cool. Flashed it without any trouble. But when I flashed, my battery was 100%. After reboot, it is showing 15%. Don't know why.
Anyways, awesome work
daemol said:
Cool. Flashed it without any trouble. But when I flashed, my battery was 100%. After reboot, it is showing 15%. Don't know why.
Anyways, awesome work
Click to expand...
Click to collapse
Thats not recovery problem. Once charge the Phone upto 100% allow two cycles of complete battery drain and analyze battery life.
As of now I'm using a deodexed modified cooked stock ROM. I have not ventured into custom Roms. Will be definitely checking out the best one and port it but I can do that only in free time like Saturday or sunday. Just tell me if you know a good one.
Sent from my E3 using xda premium
If someone is willing to help me to test my lewa is port, I can upload it. Just PM me.
Sent from my ELIFE-E3 using xda app-developers app
daemol said:
If someone is willing to help me to test my lewa is port, I can upload it. Just PM me.
Sent from my ELIFE-E3 using xda app-developers app
Click to expand...
Click to collapse
Is everything in working status in your ROM?
GODvilla said:
These are the links to custom roms recommended for Gionee E3
INFINITY HD
http://forum.xda-developers.com/showthread.php?p=44023789#post44023789
XPERIA HD
http://forum.xda-developers.com/showthread.php?p=44168616#post44168616
Click to expand...
Click to collapse
I am working on Jelly Xperia.
trip007in said:
I am working on Jelly Xperia.
Click to expand...
Click to collapse
Waiting for it :thumbup:
Sent from my ELIFE-E3 using Tapatalk 2
trip007in said:
Is everything in working status in your ROM?
Click to expand...
Click to collapse
Almost.
I can use either internal SD or external SD at any given point of time. There is some issue with mounting card on /storage/sdcard1. I can mount either on /storage/sdcard0.
can u make TRWP for e3 @OP
We need twrp from a similar device to port it. Other issue with twrp is the size of the recovery. It is bigger than the partition space alloted for the recovery on the device. We would require other tool to increase the partition size of recovery first to enable flashing the the bigger image. So its not straight forward as cwm in our case.
Sent from my GT-N7100 using xda premium
trip007in said:
We need twrp from a similar device to port it. Other issue with twrp is the size of the recovery. It is bigger than the partition space alloted for the recovery on the device. We would require other tool to increase the partition size of recovery first to enable flashing the the bigger image. So its not straight forward as cwm in our case.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
ok thanks
---------- Post added at 12:26 PM ---------- Previous post was at 12:20 PM ----------
trip007in said:
I am working on Jelly Xperia.
Click to expand...
Click to collapse
what is your status on your rom
FOR ALL GIONEE ELIFE E3 USERS WHO ARE UNABLE TO FLASH ROMS OR HAVE ANY OTHER ERROR
READ THIS
THIS WILL HELP GIONEE ELIFE E3 USERS
http://forum.xda-developers.com/showthread.php?p=44463985#post44463985
ADB in Recovery
Hi,
I am trying to get into adb when in recovery. The computer detects the devices, but throws an error. Could you please fix it?
Code:
$adb devices
List of devices attached
???????????? no permissions
$adb shell
error: insufficient permissions for device
daemol said:
Hi,
I am trying to get into adb when in recovery. The computer detects the devices, but throws an error. Could you please fix it?
Code:
$adb devices
List of devices attached
???????????? no permissions
$adb shell
error: insufficient permissions for device
Click to expand...
Click to collapse
Working absolutely fine here
trip007in said:
Working absolutely fine here
Click to expand...
Click to collapse
Let me install recovery once again and report.
Guys interested in cwm 6.0.3.3? I'm already running it on my phone. Tested working fine.
Sent from my GT-N7100 using xda premium
Resolved
daemol said:
Let me install recovery once again and report.
Click to expand...
Click to collapse
Found out the issue. The recovery is showing a different device vendor (Huawei) and the original boot.img is showing another vendor (HTC).
I had to white-list the vendor in linux (udev and ~/android/adb_usb.ini)
Now it is working fine.
Mt6589 - 4gb - jb 4.2.1
rus0001 said:
This custom recovery can recover but cannot make a backup on my fly iq4410 (blu dush analog , with 4gb ram) , when i try to make a backup i get error - can't mount /data . Who can fix it ?
Click to expand...
Click to collapse
For your device with 4GB you put CWMv6 here:
[ROM][ROOT][recovery CWM v6.0.2.8][MT6589 - 4GB - JB 4.2.1] BLU Life Play L100
TWRP for XOLO Q3000
Here is TWRP for xolo Q3000 .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I request
chinasa
@allan.vaz
@amrutb
@Jagadish-ravi
@qwerty.3551
@ravikumarbeniwal
@rohithdivakaran
@rufus.reynolds
@sushbabblu
@Vineet3
@smahalgavaiya
@vijay jay
m0han
@aabidhashmi
@barath anandan
@drlalitbida
@fort21
@nihar13
@qwerty.3551
@sanyamjain
@Sandy d Candy
@SPG30759
@ranjanshandilya
@Rishi45
@indigo110
@rahulhacker007
@sunny76900
@patilsb
@akxolo
@xoloq3000
@ravi_21
@mhp1995
@Karan_Kapuria
@nicksaisw
@Aftab Memon
@ashuchem
@Haldar_dhruv
@rohitsinghpu
@beinglazy
@viru_192
@chaobuddy
@irfanjunaid
@arnabbiswasalsodeep
@Anand Ramesh
@ashishji12
ApriliaM3
Please try this recovery and report back about JB and KK rom switching.
In TWRP 2.8 u cant root with it as supersu is deleted from recovery to reduce size.
As we have other flashable zips to root it wont be an big issue.
Waiting for response from u guys.
Credits-
@yuweng Sir this wont be possible without his tool
TWRP team
@hanuma for help:good:
avi3230 said:
In TWRP 2.8 u cant root with it as supersu is deleted from recovery to reduce size.
As we have other flashable zips to root it wont be an big issue.....
Click to expand...
Click to collapse
i'm on clone stock kk rom with cwm v6.0.2.8 now. i wanna have twrp v2.8 and also root. how best to go about it?
does your op imply "if twrp v2.7 is used, root is not lost"? - on rooted device having any other custom recovery.
and, what if i flash your twrp v2.8 and then flash supersu zip file from here? will i have proper root?
btw, can this be installed using flashify or mobileuncletools? or, is spftools procedure itself required?
suggest that you make the op clearer and noob-friendly. thanks.
m0han said:
i'm on clone stock kk rom with cwm v6.0.2.8 now. i wanna have twrp v2.8 and also root. how best to go about it?
does your op imply "if twrp v2.7 is used, root is not lost"? - on rooted device having any other custom recovery.
and, what if i flash your twrp v2.8 and then flash supersu zip file from here? will i have proper root?
btw, can this be installed using flashify or mobileuncletools? or, is spftools procedure itself required?
suggest that you make the op clearer and noob-friendly. thanks.
Click to expand...
Click to collapse
Make sure you flash stock rom first before flashing this recovery! When i was using Q900, it used to give variety of errors! So always begin with clean flashed device! The error that i got frequently was E: cannot mount /Data bla bla.... Always ended up with mounting errors! Then came Shikar bro who ported the recovery and after which i developed the custom first custom ROM!
irfanjunaid said:
Make sure you flash stock rom first before flashing this recovery! When i was using Q900, it used to give variety of errors! So always begin with clean flashed device! The error that i got frequently was E: cannot mount /Data bla bla.... Always ended up with mounting errors! Then came Shikar bro who ported the recovery and after which i developed the custom first custom ROM!
Click to expand...
Click to collapse
Anyone having this issue???
I didnt got it.
working correctly till now
but thanks for the info:good:
m0han said:
i'm on clone stock kk rom with cwm v6.0.2.8 now. i wanna have twrp v2.8 and also root. how best to go about it?
does your op imply "if twrp v2.7 is used, root is not lost"? - on rooted device having any other custom recovery.
and, what if i flash your twrp v2.8 and then flash supersu zip file from here? will i have proper root?
btw, can this be installed using flashify or mobileuncletools? or, is spftools procedure itself required?
suggest that you make the op clearer and noob-friendly. thanks.
Click to expand...
Click to collapse
U cant root using 2.8 recovery.
sometimes if rom is not rooted then at end of flash it ask u to root, 2.8 cant do that but 2.7 can:good:.
u cant have 2.8 with root facility as size will exceed 6mb.
u can root device using any flashble root zip.
================================================================================================
For kitkat 4.4.2 the zip in link is not at all useful.
Also it cant be rooted with supersu provided in recovery
so if u wanna use 2.8 u cant use rooting within recovery.
if u wanna root ur 4.4.2 see this post method 8 definatly works.
also if u want supersu as root app head over to this post.
For recovery flashing I always prefer sp tool method which will work 100% and u dont have to bother about properly rooted device.
if u have rooted device flashify or mobileuncle tool should work.
Hi Avi, when i tried to flash the recovery via flashify my stock recovery is gone as well as the one which i flashed twrp also gone and currently my phone is running without recovery
sushbabblu said:
Hi Avi, when i tried to flash the recovery via flashify my stock recovery is gone as well as the one which i flashed twrp also gone and currently my phone is running without recovery
Click to expand...
Click to collapse
Please try with sp tools.
if u running 4.4.2 flashify may give this type of error.
TWRP - 2.8 - 94 downloads:good::good::good:
avi3230 said:
TWRP - 2.8 - 94 downloads
Click to expand...
Click to collapse
weird graphics and touch issues were reported in 2.8.0.0. how about 2.8.2.0?
bovirus said:
TWRP released a bugfix for TWRP 2.8.1.0 . Now it's available TWRP 2.8.2.0.
Click to expand...
Click to collapse
m0han said:
weird graphics and touch issues were reported in 2.8.0.0. how about 2.8.2.0?
Click to expand...
Click to collapse
Yes Sir,
I ported 2.8.2.0 but the size is 6.54mb way too much than recovery partition.
I am trying much hard for more than 6 mb partition which can boot in recovery.
Already bricked my device several times for the same.
But still only 6 mb recovery can boot.
NOw we have two options.
Compile new kernel with less size - source codes are needed
we have bq codes - but it may not work for our device - so i am much reluctant to take chance.
we need to compile new uboot.bin which can make booting in recovery of even 11mb size
again source code and compiling.
If anyone from ur side can help in compiling that would be great- as i am just beginner for it
u can get source code for BQ here.
Thank you.
avi3230 said:
....If anyone from ur side can help in compiling that would be great.....
Click to expand...
Click to collapse
sorry. no knowledge in these matters. hope someone else would come forward.
avi3230 said:
...I ported 2.8.2.0 but the size is 6.54mb way too much than recovery partition.
I am trying much hard for more than 6 mb partition which can boot in recovery.....
Click to expand...
Click to collapse
any hope for latest version of twrp?
please see screenshots of twrp v2.8.0.0. the interface is not clear (highly pixelated). the actual display is worse than seen here. can anything be done about it?
does anyone know of any themes than work on twrp v2.8.0.0 for xolo q3000? the ones i tried didn't work although i chose the correct resolution.
also, what exactly does "repair or change file system" do?
my device gets connected as an mtp device and shows up as a separate device in "my computer". i mean, the sd cards do not get connected as separate usb drives.
i can open the device and see both my sd cards listed and also browse & carry out operations. but, any changes made are not reflected even after 'refreshing'.
if i click "disable mtp" as seen in the 3rd screenshot, will the disabling be temporary or permanent? will my sd cards get connected as separate usb drives?
i'd appreciate it if someone who has authentic knowledge about these matters responds with suggestions. thanks for any help.
btw, i hope @avi3230 is following this thread. maybe we can hope for ctr v3.0 kitkat for xolo q3000 soon.
edit: saw this thread only now . will try that and report :good:. please answer the queries in blue. thanks.
@m0han
TWRP 2.8.2.0 coming soon.
themes for 2.8.0.0
what exactly does "repair or change file system" do?
answer is here.
What's new in 2.7.1.0:
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
Click to expand...
Click to collapse
MTP is also mentioned under 2.8.0.0
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Click to expand...
Click to collapse
I am following CTR :good::good:
avi3230 said:
....MTP is also mentioned under 2.8.0.0....
Click to expand...
Click to collapse
i'd like to know about this:
m0han said:
....if i click "disable mtp" as seen in the 3rd screenshot,
will the disabling be temporary or permanent?
will my sd cards get connected as separate usb drives?....
Click to expand...
Click to collapse
any idea about this?
Hey guys the much awaited DualBootPatcher is here for our Condor don't believe me test out yourself
It can patch:
Custom kernels for multi support
ROMs so that they can be installed as secondary
Google Apps packages
SuperSU so that it can be used in other ROMs
xposed
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and install.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Secondary: Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of Extsd slots. These install to the external sd partition and eat up space on the external storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny and your data partition is getting full. These slots are named "extsd-slot-[id]", where "id" is something you provide in the app.
NOTE- It is highly recommended to install secondary roms in external sd slot
How To
1. Install the Multi Boot Patcher app
2. Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
3. Now go to rom settings and click on "Update ramdisk" it will update ramdisk and after that reboot
4. Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
*FLASHING FROM RECOVERY NOT RECOMMENDED*
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from the custom recovery will literally backup every ROM you have installed so think about this before making a backup.
App and data sharing
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
To use app sharing, follow these steps in every ROM that you want to use app sharing:
1.Install the app you want to share
2.Open DualBootPatcher and go to "App Sharing" in the navigation drawer
3. Enable individual app sharing
4. Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply becomes unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
FAQ's
Switch the ROM if something doesn't work properly?
If you have TWRP, you can switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
I installed a new rom and want to switch to it?
Open app, select ROMs, then select the rom you want to switch to. When the switch is successful, reboot.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Link :- https://snapshots.noobdev.io/
CREDITS
@chenxiaolong For the app
Me for porting it for you guys @princetrishi for the video
ORIGINAL THREAD
XDA:DevDB Information
Multiboot for condor , Device Specific App for the Moto E
Contributors
zeeshanhussain12
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Beta
Current Beta Version: 8.99.12
Beta Release Date: 2015-11-14
Created 2015-11-14
Last Updated 2015-11-14
Reserved
How To Report Issues ?
Getlogs.zip: getlogs.zip
If a multi-booted ROM is unable to boot, logs will be needed for debugging the issue. Please reboot into recovery without shutting down the device (ie. no removing the battery u cant remove battery in moto e [emoji14] ) and flash the GetLogs zip. This must be done immediately following the boot failure because some logs will be lost after a reboot The zip will save many logs from /sdcard/MultiBoot and device information from /dev, /proc, and /sys to /sdcard/logs/[Date&Time].tar. Please attach this tar archive when reporting an issue.
Also, state whether the ROM reboots or hangs at the moto logo or the ROM's boot animation. If the ROM reboots, please state whether it reboots into recovery or not.
NOTE- CM13 is supported
Installation Video
Thanks to YouTuber Starkdroid (@princetrishi) for making this awesome installation video!
Screenies [emoji10]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Awesome work, thanks for your hard work
And the VIDEO TUTORIAL IS HERE!!!
https://www.youtube.com/watch?v=NCk1tr6T76M&feature=youtu.be
worked
Thanks bro.... Worked for me...
Doubt
Like we flash both ROM and gapps from recovery, i cant flash it from here. I patched the ROM, flashed it, good job. But how do i flash the gapps? it shows errors. I flashed it along with the ROM. I tried the second method and flashed it after flashing the ROM...Still ain't working. Please help.
Edit : I flashed gapps seperately...and it worked!!!
Steps for those who face similar problems while patching Gapps -
1. Switch the ROM from Dual Boot Patcher.
2. Reboot your phone. If you flashed correctly, you should be on the secondary ROM....
3. Reboot to recovery and flash gapps. No need to wipe cache/dalvik cache.
4. Woila! Gapps flashed successfully!
Hit Thanks Button if I Helped!!!
The Keeper said:
Like we flash both ROM and gapps from recovery, i cant flash it from here. I patched the ROM, flashed it, good job. But how do i flash the gapps? it shows errors. I flashed it along with the ROM. I tried the second method and flashed it after flashing the ROM...Still ain't working. Please help.
Click to expand...
Click to collapse
You need to patch gapps too [emoji6] and flash it from the app itself
Sent from my Moto E using Tapatalk
The Keeper said:
No....I tried. It doesn't work. It fails.
Click to expand...
Click to collapse
Its working for me, make sure you patch for correct slot
Sent from my Moto E using Tapatalk
Hey...will this work with cm13 as primary rom?
can this work with cm13 as secondary rom?
ishu.aryan said:
can this work with cm13 as secondary rom?
Click to expand...
Click to collapse
Nop cm13 is not supported in both primary and secondary ROM , I m still working on that part mate
Adrao123 said:
Hey...will this work with cm13 as primary rom?
Click to expand...
Click to collapse
Sent from my Moto E using Tapatalk
Thanks for the port
I was waiting for lp support of multirom, and then you ported multiboot, this is far better than multirom..
The Keeper said:
Like we flash both ROM and gapps from recovery, i cant flash it from here. I patched the ROM, flashed it, good job. But how do i flash the gapps? it shows errors. I flashed it along with the ROM. I tried the second method and flashed it after flashing the ROM...Still ain't working. Please help.
Click to expand...
Click to collapse
Bro try different gaaps..
Few gapps didn't worked even for me..
But at last I was able to flash
viku1996 said:
Bro try different gaaps..
Few gapps didn't worked even for me..
But at last I was able to flash
Click to expand...
Click to collapse
umm..okay...Thanks
It shows failed to update ramdisk for me... Help plz..
Sent from my Moto E using Tapatalk
Please be more precise and which ROM you are using?
Note - cm13 is not supported
Gowtham_j said:
It shows failed to update ramdisk for me... Help plz..
Sent from my Moto E using Tapatalk
Click to expand...
Click to collapse
Sent from my Moto E using Tapatalk
I'm on exodus 5.1. I've followed the steps as quoted in the op. After setting the kernel I tried to update the ramdisk, but I faced an error. It shows "failed to update ramdisk".
Gowtham_j said:
I'm on exodus 5.1. I've followed the steps as quoted in the op. After setting the kernel I tried to update the ramdisk, but I faced an error. It shows "failed to update ramdisk".
Click to expand...
Click to collapse
It was working for my friend. Please upload ramdisk update log . it will be there in multiboot folder
Sent from my Moto E using Tapatalk
if i wanna flash xposed
then should i patch xposed zip too?
lenovo a536 custom rom[UPDATED]
MIUI 7
note:* I am not the developer of these roms and i am not responsible for any bricked devices
MIUI 7 (by miuipro):
Description
No bugs, Super smooth, Worked all.
Differences firmware on the current day
1 MIUI.SU - Drivers are translated using the utility the BARS ,large set of patches as previously written still firmware suitable for testers no patches available, the extended menu has reboot. Firmware Deodexed.
2 Xiaomi.eu - A set of patches is almost completely expanded menu has no reboot, the patch is not available. To transfer using Jbart .
impressive number of features included . Firmware Deodexed.
3 MIUIPRO - a large set of patches is available from which you can select a patch and can use without authorization Mi account ,the expanded menu has restart, fine when calling.
Firmware Deodexed.
4 Multirom.me - Drivers are based on the basis of its own repository. Manuals Methic . Of the features : a very good optimization of RAM.
The patches around 40.
Sometimes more, sometimes less.
At the moment - exactly 40.
Also widely known T9 patches and patch third-party themes are present:
Patch Anti-spam, calendar (Russian and Ukrainian holidays), camera, wedge-master, e-mail, gallery, a compass, a framework, Mui keyguard, framework, weather, sMS, yellow pages, security center, videos, contacts, and so on. In general, patches adapted typical Chinese setting and services to European. (Many are present in the firmware of other localization) Firmware Deodexed
screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Main features:
HTML:
#Optimization of the system as a whole.
#The updated browser without graphic bugs.
#Good sound ( compare with the iPhone 5S)
#Powered equalizer and amplifier MiSound.
#Visual graphics improvement.
#Loud sound due libraries Xiaomi.
#SD card as the memory by default.
#Perhaps something more but I forgot
.
dowload:
http://miuipro.ru/rommgr/device_view/443
Click to expand...
Click to collapse
NEW
MIUI 7 From others:
MIUI 7 6.4.14 from MIUI.SU
MIUI 7 6.4.14 from MIUIPRO
MIUI 7 6.4.14 from Xiaomi.eu
MIUI 7 6.4.14 from Multirom.me
Fix Task Manager for multirom.me firmware
Click to expand...
Click to collapse
How to install? I want to test on my wife phone
Please tell me the steps. Thanks in advance
LATER EDIT:
Installing from TWRP Recovery
ionutmaruta said:
How to install? I want to test on my wife phone
Please tell me the steps. Thanks in advance
LATER EDIT:
Installing from TWRP Recovery
Click to expand...
Click to collapse
INSTALL STEPS
1.go to twrp
2.mount data,cache,system.
3.clear/format cache,format data , format system
4.install zip file from sd card(please put downloaded zip file root directory )
5.reboot to system( it take some minutes for 1st boot be patient)
Solved. Thanks anyway
I like MIUI. More better than stock rom
ionutmaruta said:
Solved. Thanks anyway
I like MIUI. More better than stock rom
Click to expand...
Click to collapse
me too bro
v5.12.10 not working anymore
Just updated succesfully, the device restarting but remain in boot loop with LENOVO powered by android
Just recovery the previous version from my TWRP backup, installed again the new version 5.12.10 from external, then from internal sd card, but the same issue ?
What can I do ? I can't update it anymore
ionutmaruta said:
v5.12.10 not working anymore
Just updated succesfully, the device restarting but remain in boot loop with LENOVO powered by android
Just recovery the previous version from my TWRP backup, installed again the new version 5.12.10 from external, then from internal sd card, but the same issue ?
What can I do ? I can't update it anymore
Click to expand...
Click to collapse
did u flash successfully.check twrp flash details(some twrp version have some mount bugs check that first )
if problem still there
try to wipe data,wipe cache,wipe system and then flash new update
Is it possible to port the same on lenovo P1m
I would love to have miui ( from xioami mi4i) onto lenovo P1m
is it possible... ?
mtk_xda said:
I would love to have miui ( from xioami mi4i) onto lenovo P1m
is it possible... ?
Click to expand...
Click to collapse
sry dude.but it can be ported.
upto current status
the available roms are:
AOSP 5.1
FLYME 4.5
VIBE UI 3.0
MINIMOD
rejul said:
did u flash successfully.check twrp flash details(some twrp version have some mount bugs check that first )
if problem still there
try to wipe data,wipe cache,wipe system and then flash new update
Click to expand...
Click to collapse
I do that. Not working anymore
ionutmaruta said:
I do that. Not working anymore
Click to expand...
Click to collapse
check your twrp recovery bro .is it mounting system,data,cache.
make sure data is mounted
i actually had twrp. and had similar problem that is cant flash any other(reason: data cant be mounted)
try use CWM recovery
here is the link http://www.mediafire.com/download/vi81bth685jmyry/Cwm_revover_lenovo_a536.rar
use sp flash tool
scatter file and img file included in zip
rejul said:
check your twrp recovery bro .is it mounting system,data,cache.
make sure data is mounted
i actually had twrp. and had similar problem that is cant flash any other(reason: data cant be mounted)
try use CWM recovery
Click to expand...
Click to collapse
I have TWRP v2.8.1.0 and is working fine with the previsous versions.
Beside I cand backup and recovery the data only without problems
Like I said, the installation of MIUI 5.12.10 is finished, but after restart the phone remain in boot loop
I don't think that is from TWRP, believe me, because the OS must be automatically configured without data ! The phone must be show me something like that....
ionutmaruta said:
I have TWRP v2.8.1.0 and is working fine with the previsous versions.
Beside I cand backup and recovery the data only without problems
Like I said, the installation of MIUI 5.12.10 is finished, but after restart the phone remain in boot loop
I don't think that is from TWRP, believe me !
Click to expand...
Click to collapse
CHECK
can you post log
ionutmaruta said:
I have TWRP v2.8.1.0 and is working fine with the previsous versions.
Beside I cand backup and recovery the data only without problems
Like I said, the installation of MIUI 5.12.10 is finished, but after restart the phone remain in boot loop
I don't think that is from TWRP, believe me, because the OS must be automatically configured without data ! The phone must be show me something like that....
Click to expand...
Click to collapse
BRO i actually flashed it had no problem.
i am cwm
their is bug in twrp for our phone(it cant mount data sometimes)
during the first flash it was fine for me then after i had this problem.2-3 days i waS worried after i figured and installed cwm and finally problem is over
I don't have a log and I don't have the phone near me. It's my wife phone
Which is the last version of CWM for A536 ?
Can you PM the last version of CWM ?
ionutmaruta said:
I don't have a log and I don't have the phone near me. It's my wife phone
Which is the last version of CWM for A536 ?
Can you PM the last version of CWM ?
Click to expand...
Click to collapse
http://www.mediafire.com/download/vi81bth685jmyry/Cwm+revover+lenovo+a536.rar
use sp flash scatter file and recovery img inside
Thanks. I'll try today
But I don't understand why the TWRP not installing this version of MIUI, but install all of the previous versions without problems
ionutmaruta said:
v5.12.10 not working anymore
Just updated succesfully, the device restarting but remain in boot loop with LENOVO powered by android
Just recovery the previous version from my TWRP backup, installed again the new version 5.12.10 from external, then from internal sd card, but the same issue ?
What can I do ? I can't update it anymore
Click to expand...
Click to collapse
Hi, bro.
It's also happen to me..
Does using cwm fixing the problem?
Installed CWM Recovery, but I can't backup my nandroid and I can't install the last version of MIUI.
It show me error, then back to the main screen of CWM recovery
If I want to make a backup it return invalid path
I think this version of CWM is a crap
TESTED with all custom recovery which I have.
1. Your CWM recovery (Has internal errors)
2. Philz touch recovery v6.59.0 (A536)
3. TWRP RECOVERY v2.7.1.1
4. TWRP RECOVERY v2.8.1.0
5. TWRP RECOVERY v2.8.6.0
I can install the new version of MIUI with all custom recovery, but the phone restart in boot loop with logo "Lenovo powered by android" and stay there...
What can I do ?
I have to wait for a new version of MIUI