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?
Related
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
Dear XOLO Q 3000 users,
I customized the stock ROM of Xolo Q3000 and porting it here. The CWM recovery was extracted from the Droid tool. Though it is rooted one to get shell root kindly use Explore.apk and provide read write permission.
The rom can be downloaded from the google drive url: https://drive.google.com/file/d/0Bz8Fgu4wkBnqYzEzWE5Fd2N2ajQ/edit?usp=sharing
I have already provided the recovery file in an earlier porting.
If there is anything more please ask for. I am Modding the HDC note3 4.3.1 ROM the camera is still a problem. I will port screen shots and the rom soon.
Extract CWM recovery form the .tar file from the url below and t and use mobileuncle tool to install it, if you are already not installed CWM in your phone.
url:https://drive.google.com/file/d/0Bz8Fgu4wkBnqeHdPeDhEVnViQXM/edit?usp=sharing
Hiii
I am also a user of Q3000.
Looking for custom roms.
My phone version is XOLO_Q3000_S003_15102013.
What version is urs?
Our phone is actually rebranded
Q3000 is rebranded from bq aquaris 5.7
http://www.bqreaders.com/gb/products/aquaris-5-7.html
After some search I found a forum for this phone and there are few roms
Modified stock rom for q3000
http://www.htcmania.com/archive/index.php/t-768108.html
u can find more roms in following links
http://www.androidpt.com/index.php?/topic/52527-aquaris-57-rootrecoveryroms-24042014/
I tried CWM by http://forum.xda-developers.com/showthread.php?t=2638400
but no help.
I used ctr 2.1 recovery which worked.
I also tried stock and MIUI rom from HTC mania but no help.
Can u please download MIUI rom and stock q3000 rom and see if it works in ur phone and let me know.
Thanks in advance.
Stock q3000 is already working for me.
Based on that only I have provided the rooted custom ROM.
Have you tried the above ported ROM.
You may have to choose a correct boot.img file for a successful flash and boot there on.
You can use mobileuncle tool to get your cwm recovery
I am just downloading MUII ROM AND TRY.
I am still succeed to make camera working in S4 and Note3 ROMs of 4.3 versions
Sent from my Q3000 using xda app-developers app
avi3230 said:
Hiii
I am also a user of Q3000.
Looking for custom roms.
My phone version is XOLO_Q3000_S003_15102013.
What version is urs?
Our phone is actually rebranded
Q3000 is rebranded from bq aquaris 5.7
http://www.bqreaders.com/gb/products/aquaris-5-7.html
After some search I found a forum for this phone and there are few roms
Modified stock rom for q3000
http://www.htcmania.com/archive/index.php/t-768108.html
u can find more roms in following links
http://www.androidpt.com/index.php?/topic/52527-aquaris-57-rootrecoveryroms-24042014/
I tried CWM by http://forum.xda-developers.com/showthread.php?t=2638400
but no help.
I used ctr 2.1 recovery which worked.
I also tried stock and MIUI rom from HTC mania but no help.
Can u please download MIUI rom and stock q3000 rom and see if it works in ur phone and let me know.
Thanks in advance.
Click to expand...
Click to collapse
Thanks for your thrust.
I was able to mode the few MIUI roms and MIUI Rom of ZP980 4.4 and Kit kate roms for our XOLO Q3000 I am still fine tuning it and I hope to release it today evening or night.
I have normal version and AROMA version modded.
The problem is in MIUI roms the phone storage of 12 GB or more is not visible. IF i could not I will port and then latter we will rectify them one by one. Further after pop up of Logo, the phone become black and after 2 minutes it boot to normal when we press power button. I am trying to rectify it.
Please wait till today.
In the mean time I port here a CWM flashable version of Carliv Touch Recovery V 2.2 based MTK v6 6.0.4.4 both AROMA Version and a normal flashable.
Further you can extract the recovery file and flash it through Smart phone "Flash Tool or through Mobileuncle Tool
If you have any difficulties in booting your phone I am also porting the stock boot image extracted from my phone.
Thanks for your interest
X0lo q3000 stock based miui rom
puduraja said:
Thanks for your thrust.
I was able to mode the few MIUI roms and MIUI Rom of ZP980 4.4 and Kit kate roms for our XOLO Q3000 I am still fine tuning it and I hope to release it today evening or night.
I have normal version and AROMA version modded.
The problem is in MIUI roms the phone storage of 12 GB or more is not visible. IF i could not I will port and then latter we will rectify them one by one. Further after pop up of Logo, the phone become black and after 2 minutes it boot to normal when we press power button. I am trying to rectify it.
Please wait till today.
In the mean time I port here a CWM flashable version of Carliv Touch Recovery V 2.2 based MTK v6 6.0.4.4 both AROMA Version and a normal flashable.
Further you can extract the recovery file and flash it through Smart phone "Flash Tool or through Mobileuncle Tool
If you have any difficulties in booting your phone I am also porting the stock boot image extracted from my phone.
Thanks for your interest
Click to expand...
Click to collapse
I am providing below the google drive url where the X0LO Q3000 STOCK BASED MIUI is ported.
Before doing anything kindly back up your ROM and IMEI and all data.
The Rom is modded from one of the roms available in the http://www.androidpt.com/index.php?/...roms-24042014/. It has been modded by copying files from other roms and most of them from the stock XOLO Q3000 rom.
I can not say all of them are working but most of the features are working. This is the first time I am using the MIUI Rom and it looks more customer friendly.
You have to be little patient. After pop up of Logo, the screen go black but boots up nearly after 90 seconds or 2 minutes with the boot sound. and hence do not panic.
I shall try to rectify what all required if I hear from you.
Procedure:
1. Down load the ROM from the url: Google Drive: https://drive.google.com/file/d/0Bz8Fgu4wkBnqNExrU0doV0lXS2s/edit?usp=sharing
2. take it as it is to your internal or external sd card.
3. save your rom, data and IMEI.
The IMEI can be backed up by using Mobile uncle Tool, in case of you loosing it. It did not happen to me. but as a cautin it is always better.
3. Go to recovery and Wipe all data, system and catche using any one of the recovery method with has been ported earlier.
4. Now go to te ROM zip file you have just copied and flash it.
5. Wait for one or 2 minutes. After pop up of Logo and appearance of bloack screen, the signal icons at the bottom will glow and you may here booting audio sound.
6. Now press the power button and your screen will glitter with lockscreen.
7. Follow the instructions there on.
8. After entering the MIUI Lock screen first you search for the SuperSU and click it. Install it. Now your phone is rooted. Without doing it it is difficult to achieve root. This was poping in the first pop and goes away if we do not care it in the original one. Now for convenience it has been put to leisure activity. If you do not want to root your phone do not bother about it.
Enjoy.
There are some more ROMs are on pipe line, after hearing the response I shall port them, mainly due to time constrains, it is delayed.
Hello, thank you for the touch recovery.. Brother can you please provide a kit-kat rom for this phone...I found your thread on xda which has kit-kat rom...does that rom work well with this phone..does it have any bugs/lags etc..
Already ported in a new thread. Please scout.
Thanks for encouragement.
Sent from my Q3000 using xda app-developers app
No bugs to my knowledge. You may verify and report. I shall try to provide solution.
Just by appropriate changes of files these MTK phones may accommodate other phones toms also
Sent from my Q3000 using xda app-developers app
Hiii
tried ur stock rom and miui
Why the internal storage is only 2 gb.
I am not using any external card as our phone has 16 gb internal.
if i install ur roms internal storage is not shown as it is.
instead it shows only 2 gb ???
Any solution for this??
I alrady posted in this thread regarding BQ aquaris 5.7 roms (same as our phone)
in those roms u can see internal stoarage of 16gb ??? How???
http://www.htcmania.com/showthread.php?t=772316 (see this link)
If we first flash the bq stock Rom with SP tool flasher, notice there they have given only EBR1. But no EBR2. You will get both internal and phone storage.
If you flash that Rom in XOLO you get internal storage 12 GB, external SD plus phone storage further 16 GB.
I tried other SP Flashable ROMs with that EBR1 File but phone did not boot at all.
Please note this. You open the ROM FILE, open the system, open the etc folder.
Now search for the extra vold2.fstab file and remove it from the folder. Do these edit operations remaining in the zip folder.
Flash the Custom Rom and try the enhanced storage just by flashing as you did, may ebr1 and ebr2 alone.
Format factory /data. Reboot.
Now the internal storage will be visible.
Try
Otherwise please wait till I port how we can increase the storage to 1.93 GB 2.46 GB 7 GB . My test reveals stock Rom works fine. Kit Kat Rom works fine I have 2 more ROMs I will check them tonight and port. I have up loaded the files to Google drive
7 GB in first boot do no recognise second SIM but third boot it functions.
.
I will test MIUI Rom and port tonight or tomorrow.
Thanks for reminding me.
You remove the extra Void file provided
If flash the bq stock Rom
Sent from my Q3000 using xda app-developers app
avi3230 said:
Hiii
tried ur stock rom and miui
Why the internal storage is only 2 gb.
I am not using any external card as our phone has 16 gb internal.
if i install ur roms internal storage is not shown as it is.
instead it shows only 2 gb ???
Any solution for this??
I alrady posted in this thread regarding BQ aquaris 5.7 roms (same as our phone)
in those roms u can see internal stoarage of 16gb ??? How???
http://www.htcmania.com/showthread.php?t=772316 (see this link)
Click to expand...
Click to collapse
After giving you the earlier reply I cross checkd flashing the AROMA MIUI rom ported here by me. please look at the screen shots and lap top image.
Actually the sd stgorage is there but not visblke in the storage like other ROMs. But by using EXplore if you go to storage folder of the device you can see it.
In computer both sd cards are seen and you can do the editing. This is when the phone is in the Media stage. In USB only the external storage is shown.
Actually tghe 1.93 which you have seen in your storage is the internal storage and the remaining is not shown but you can edit the files through computer in the Media mode.
LOOK at the screen shots:
{
"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"
}
This screen shots are from the AROMA looped MIUI rom after the removal of vol2.fstab from the etc folder. with 7.04 GB internal storage and 6.96 phone storage.
puduraja said:
After giving you the earlier reply I cross checkd flashing the AROMA MIUI rom ported here by me. please look at the screen shots and lap top image.
Actually the sd stgorage is there but not visblke in the storage like other ROMs. But by using EXplore if you go to storage folder of the device you can see it.
In computer both sd cards are seen and you can do the editing. This is when the phone is in the Media stage. In USB only the external storage is shown.
Actually tghe 1.93 which you have seen in your storage is the internal storage and the remaining is not shown but you can edit the files through computer in the Media mode.
LOOK at the screen shots:
View attachment 2743694
View attachment 2743693
View attachment 2743717
This screen shots are from the AROMA looped MIUI rom after the removal of vol2.fstab from the etc folder. with 7.04 GB internal storage and 6.96 phone storage.
Click to expand...
Click to collapse
Tried removing vold2 file but still got only 1gb drive only
also tired replacing vold files from stock rom still no luck
In my MIUI cant connect as media storage (using windows 7 )
so cant see two diff parts as u can see (phone and internal storage)
Will wait for ur further rom.
I also tried stock rom from htcmania.
but again same 2gb internal only.
(this stock rom is deodexed, zipalined)
Will try any other rom u wish to try.
Thanks for ur support.
Good luck for further rom developing.
---------- Post added at 12:16 AM ---------- Previous post was at 12:11 AM ----------
Please make a single thread for this device so people can find things at one place.
Just post the links for the roms, recoveries etc at first post and keep updating.
it will be easy for u too (I think so)
Its just a suggestion.
for example
http://forum.xda-developers.com/showthread.php?t=2359221
avi3230 said:
Tried removing vold2 file but still got only 1gb drive only
also tired replacing vold files from stock rom still no luck
In my MIUI cant connect as media storage (using windows 7 )
so cant see two diff parts as u can see (phone and internal storage)
Will wait for ur further rom.
I also tried stock rom from htcmania.
but again same 2gb internal only.
(this stock rom is deodexed, zipalined)
Will try any other rom u wish to try.
Thanks for ur support.
Good luck for further rom developing.
---------- Post added at 12:16 AM ---------- Previous post was at 12:11 AM ----------
Please make a single thread for this device so people can find things at one place.
Just post the links for the roms, recoveries etc at first post and keep updating.
it will be easy for u too (I think so)
Its just a suggestion.
for example
http://forum.xda-developers.com/showthread.php?t=2359221
Click to expand...
Click to collapse
1. I am confused. Your phone is xolo or bq aquiris.
If it is Xolo you flash xolo stock rom that has come with the phone. see my latest where I have ported smart tool flashable stock rom.
2. Now HOW TO START all about XOLO Q3000 just tell me how to put every thing at one place to ease the users of this phone.
3. is it to copy and paste, I casually started now one by one is comming. please guide me or you take the lead just by pull togather to one place..
You might have seen the latest one.
Haute we the
http://forum.xda-developers.com/showthread.php?t=2753196
At the end I have uploaded the stock Rom along with different storages that you can choose for your phone.
The operations also given. Hope you will correct the booting and other problems
If you feel any diffIculty please write here or pm
Sent from my Q3000 using xda app-developers app
@puduraja i have purchased xolo q1010i.i want to extract its boot.img.how can it be possible.its rooted.
for the system data i thought to copy whole system folder by using any root explorer.is it the right way...and pls...can you pls provide cwm of this phone.
puduraja said:
....I port here a CWM flashable version of Carliv Touch Recovery V 2.2 based MTK v6 6.0.4.4 both AROMA Version and a normal flashable.
Further you can extract the recovery file and flash it through Smart phone "Flash Tool or through Mobileuncle Tool
If you have any difficulties in booting your phone I am also porting the stock boot image extracted from my phone.
Click to expand...
Click to collapse
i've downloaded all 3 files attached here. but, before i proceed, i'd like a clarification/confirmation:
i understand there are several build nos., depending on how old/recent your device is.
i've seen XOLO_Q3000_S003_15102013 here, XOLO_Q3000_S009_02122013 here etc. mine is XOLO_Q3000_S011_25022014.
is the recovery.img present in the attached files here usable on all these devices (irrespective of the build no.)?
i've already extracted it. md5 checksum: 68e91ef520a215cd029d8606c489aed7. can i install it using Mobileuncle Tools safely?
@puduraja, @Vineet3, @avi3230, please answer/help. thanks in advance.
m0han said:
i've downloaded all 3 files attached here. but, before i proceed, i'd like a clarification/confirmation:
i understand there are several build nos., depending on how old/recent your device is.
i've seen XOLO_Q3000_S003_15102013 here, XOLO_Q3000_S009_02122013 here etc. mine is XOLO_Q3000_S011_25022014.
is the recovery.img present in the attached files here usable on all these devices (irrespective of the build no.)?
i've already extracted it. md5 checksum: 68e91ef520a215cd029d8606c489aed7. can i install it using Mobileuncle Tools safely?
@puduraja, @Vineet3, @avi3230, please answer/help. thanks in advance.
Click to expand...
Click to collapse
DEARFriend,
The recovery extracted depends on the boot.img that is used. If the boot.img of yours and the extracted recovery at that time is same then it can be used. Otherwise some functions may not work in the recovery, even it accepts the recovery.img. This is my experience. As I informed the XOLO Q3000 accepts three diffeent boot .img file and perfectly boots up. But the Carliv recovery which I have ported in my AROMA pertain to the stock boot.img file.
But ithe same also is used in MIUI ROMs customized by me. It is working normal. It mostly depends on the size of the .img files in general
m0han said:
i've downloaded all 3 files attached here. but, before i proceed, i'd like a clarification/confirmation:
i understand there are several build nos., depending on how old/recent your device is.
i've seen XOLO_Q3000_S003_15102013 here, XOLO_Q3000_S009_02122013 here etc. mine is XOLO_Q3000_S011_25022014.
is the recovery.img present in the attached files here usable on all these devices (irrespective of the build no.)?
i've already extracted it. md5 checksum: 68e91ef520a215cd029d8606c489aed7. can i install it using Mobileuncle Tools safely?
@puduraja, @Vineet3, @avi3230, please answer/help. thanks in advance.
Click to expand...
Click to collapse
If u have doubts regarding recovery.
u can just try it without installing it by booting in recovery not flashing it.
for this purpose u need adb tools and windows.
First install drivers for phone. (http://ge.tt/2yL21VT/v/2)
use adb tools (http://forum.xda-developers.com/showthread.php?t=1474956)
extract adb tools in a dir preferably on c:\
put ur desired recovery in same folder
connect ur phone with usb cable
now goto command prompt (cmd)
goto adb directory
type adb reboot bootloader (so ur phone wil restart and stop at xolo logo)
then type fastboot boot (the recovery name).img (this will on boot in particular recovery without flashing it.
if it boot in recovery means its working
by this method u can just backup ur stock rom with stock recovery.
if u want perment cwm recovery then flash it.
using fastboot flash recovery.img
m0han said:
i've downloaded all 3 files attached here. but, before i proceed, i'd like a clarification/confirmation:
i understand there are several build nos., depending on how old/recent your device is.
i've seen XOLO_Q3000_S003_15102013 here, XOLO_Q3000_S009_02122013 here etc. mine is XOLO_Q3000_S011_25022014.
is the recovery.img present in the attached files here usable on all these devices (irrespective of the build no.)?
i've already extracted it. md5 checksum: 68e91ef520a215cd029d8606c489aed7. can i install it using Mobileuncle Tools safely?
@puduraja, @Vineet3, @avi3230, please answer/help. thanks in advance.
Click to expand...
Click to collapse
Dear friend,
if you can port your boot.img of your stock 114 model phone (XOLO Q3000 114), I can provide you the CWM and Carlive touch recovery.
Regards and thanks.
Please help as there is no custom ROM for xolo q1000s. Pls make a custom ROM for this device.
Sent from my Q1000S using XDA Free mobile app
TWRP RECOVERY - 2.8.1.0 - XOLO Q3000
Procedure to follow
extract TWRP.zip to internal sd card & external sd card (both)
it should be in root of both as shown in the picture.
{
"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 path should be sd card(int & ext) /TWRP/theme/ui.zip
then flash twrp recovery using sptools.
This is fully working recovery - tested by me.
flashed JB & KK rom.
Backup and restore without any issues.
Try and report.
For official change logs, see here:
http://teamw.in/project/twrp2
Credits:-
master Yuweng Sir. - for TWRP 2.8.1.0 tool.
Santhosh M - for making it work on XOLO Q3K by reducing the size to 6 MB.:good::good:
It was more than 6 mb in size.
SCREEN SHOTS OF RECOVERYcan be taken as normal SS (power & vol down)
SS stored in int storage/pictures/screenshots/
Credits:-
Santosh M
TWRP Materialised Themes- Dark / Light / Play by z31s1g
Thread link
How to install:
Download the theme of your choice and rename it to "ui.zip".
On SD card (if device has internal and external storage, use the internal) open TWRP folder and create a folder called "theme", without capital letters.
Copy ui.zip to theme folder.
Restart to recovery.
Previews:
Screenshot Gallery
Download link
dont download multirom themes.
Full credit goes to z31s1g
After more than 24 hours , 14 download
still waiting for a thanks and a reply.
Finally.....
Still no reply.
Has anyone used this recovery - please post the review.
avi3230 said:
TWRP RECOVERY - 2.8.1.0 - XOLO Q3000
.....the path should be sd card(int & ext) /TWRP/theme/ui.zip.....
Santhosh M - .... reducing the size to 6 MB.....
Click to expand...
Click to collapse
do these themes work only on v2.8.1.0? i'd tried some themes on twrp v2.8.0.0. they did not work.
which folder should one chose themes from? TWRP 281X or TWRP 281X_v2?
many thanks to Santhosh M for his positive response :highfive:. keep up the good work, avi3230 :good:.
---------- Post added at 02:37 PM ---------- Previous post was at 02:10 PM ----------
avi3230 said:
....Has anyone used this recovery - please post the review.
Click to expand...
Click to collapse
i intend to when i'm not pressed for time. will post my experience with it.
themes from here did not work for me on twrp v2.8.0.0 in the recent past.
does aroma file manager work in twrp v2.8.1.0?
avi3230 said:
....can be take as normal SS (power & vol down)
SS stored in int storage/pictures/screenshots/.....
Click to expand...
Click to collapse
tried this in twrp v2.8.0.0. works! :highfive:
stuck in 'gallery'; can't swipe to the next/previous image.
avi3230 said:
.....extract TWRP.zip to internal sd card & external sd card (both)
the path should be sd card(int & ext) /TWRP/theme/ui.zip
then flash twrp recovery using sptools.....
Click to expand...
Click to collapse
did exactly as above. no booting into recovery.
then tried mobileuncletools. no go.
also tried the 'dd' way. no go.
Code:
su
dd if=/sdcard/recovery.img of=/dev/recovery
tried twrp v2.7.1.0. worked. tried twrp v2.8.0.0. worked. twrp v2.8.1.0 does not work - for me, at least.
the theme does not work, in any case.
m0han said:
did exactly as above. no booting into recovery.
then tried mobileuncletools. no go.
in any case.
Click to expand...
Click to collapse
Sir I have taken screenshots in same recovery.
It worked for me.
I booted in recovery
via phone (gravity box - advanced boot menu)
Power+vol button method too.
I dont know exactly why this happening with u.
try flashing with sptools.
avi3230 said:
....try flashing with sptools.
Click to expand...
Click to collapse
read again....
avi3230 said:
.....extract TWRP.zip to internal sd card & external sd card (both)
the path should be sd card(int & ext) /TWRP/theme/ui.zip
then flash twrp recovery using sptools.....
Click to expand...
Click to collapse
m0han said:
did exactly as above.....
Click to expand...
Click to collapse
avi3230 said:
....try flashing with sptools.
Click to expand...
Click to collapse
well, i did more. read on....
i'm running stock kk rom of this device (clone of xolo q3000). the firmware hard reset package (kitkat 4.4.2) of that device is this zip file, found at the bottom of the above page.
thinking that not running original xolo stock firmware was causing twrp v2.8.1.0 to not work, i 'sp-flash'ed (firmware upgrade) orignal kk stock rom of xolo q3000 and then 'sp-flash'ed twrp v2.8.1.0. still, twrp v2.8.1.0 would not work. so, i got back on twrp v2.8.0.0 and flashed [custom kk rom] deodexed s005 rom. it installed fine. the first thing i tried was whether my usual onandroid backup script works. it does not. it works well in that clone stock rom, though.
i've made several requests in various threads and also pm'ed avi3230 about this. although he said he'd look into it long back, i believe he's not free from his rom cooking to find time for my request. but, i'll keep hoping :fingers-crossed:. you see, the whole process of checking whether that script works (including taking a full backup) takes less than 5 min. i'd love to be on stock deodexed kitkat rom of my very own device.
i believe i'm giving pretty much honest feedback about @avi3230's work. is it too much to expect help regarding some legitimate issues? i don't know how hard this is, but, a comparison of the storage implementation and/or other apsects of both roms could help identify the trick to get the script to work on stock kk rom.
i'm willing to provide files from backups of both clone rom and stock rom, if anyone is willing to help. thanks in advance for any help.
m0han said:
well, i did more. read on....
....thanks in advance for any help.
Click to expand...
Click to collapse
Sorry Sir I havnt tested ur app till now.
If u see the basic difference in BQ and Xolo is shared sd card.
If u decompile boot.img of both u will see shared sd card allowed in xolo not in BQ.
This is the main reason the app not working properly in xolo.
I am trying to make a device tree for our device so that we can port CM, PA, omni rom to our device.
BUt there are many issues with starting the project itself.
Santosh Sir is helping me out.
He already successfully booted Lollipop (omnirom based) on MMX A117.
Also smokerman sir trying to find solution for above thing as there is issues of storage's.
Anyone using TWRP 2.8.1.0
please give feedback.
@m0han sir not able to boot in recovery.
Anyone with same issue.
Please reply so that i can post 2.8.2.0.
avi3230 said:
....the basic difference in BQ and Xolo is shared sd card.
....decompile boot.img of both u will see shared sd card allowed in xolo not in BQ.
........we can port CM, PA, omni rom to our device......many issues with starting the project itself......
Click to expand...
Click to collapse
"shared sd card allowed in xolo not in BQ". i'm not sure i get you. did you mean vice versa, by any chance?
btw, can boot.img of bq be used in stock deodexed xolo? will that work for full sdcard read+write access?
it'd be cool if you can troubleshoot a basic problem as the above, while still getting a kick out of porting roms.
avi3230 said:
Anyone using TWRP 2.8.1.0 .....reply so that i can post 2.8.2.0.
Click to expand...
Click to collapse
what does the silence mean, i wonder. no one using twrp v2.8.1.0? or everyone has it working well?
m0han said:
......
what does the silence mean, i wonder. no one using twrp v2.8.1.0? or everyone has it working well?
Click to expand...
Click to collapse
we cant use boot image of one rom in other because of the same reason - shared sd card.
If u use u may brick ur device - i already tried it.
I am behind this same issue as it is the key for further development of the device as source codes of BQ are available.
About TWRP already 70 download and no reply, dont know why??
I already have TWRP 2.8.2.0 and CTR 3 working.
After some replies here I will post them.
CTR still need some testing .
Thank you.
avi3230 said:
.....I already have TWRP 2.8.2.0 and CTR 3 working.
After some replies here I will post them.
CTR still need some testing....
Click to expand...
Click to collapse
going by the trend of replies, i doubt you'll be able to release them anytime soon.
ctr 3 would be the latest; maybe a refreshing change from twrp. 'some testing' regarding what?
m0han said:
going by the trend of replies, i doubt you'll be able to release them anytime soon.
ctr 3 would be the latest; maybe a refreshing change from twrp. 'some testing' regarding what?
Click to expand...
Click to collapse
There is not much change in TWRP 2.8.2 atleast in GUI but codes are much different - check here changelog.
Master Carliv changed some part of script which is related to sd card.
I was facing error in sd card.
Now i am going through it again and will post final recovery soon.
avi3230 said:
Anyone using TWRP 2.8.1.0
please give feedback.
@m0han sir not able to boot in recovery.
Anyone with same issue.
..............
Click to expand...
Click to collapse
TWRP 2.8.1.0 is working fine.
@Sagar_Patel confirmed its working and also backup & restore is working normally.
TWRP_2.8.1.0
m0han said:
did exactly as above. no booting into recovery.
then tried mobileuncletools. no go.
also tried the 'dd' way. no go.
Code:
su
dd if=/sdcard/recovery.img of=/dev/recovery
tried twrp v2.7.1.0. worked. tried twrp v2.8.0.0. worked. twrp v2.8.1.0 does not work - for me, at least.
the theme does not work, in any case.
Click to expand...
Click to collapse
Hello sir, i am posting here to confirm that twrp v2.8.1.0 was working absolutely fine (at least for a while!!!) ...no problem for taking backup and restore...however, after using couple of hours (i was trying link2sd but device could not manage with 32 gb msdhc, worked fine with 16 gb msdhc), when i tried to go into recovery, it was crashed...not even adb reboot recovery worked...dont know why...but reflashed again and had same issue...now using PhilZ 2.57.9
By the way, had great support from avi3230 sir....
avi3230 said:
I already have TWRP 2.8.2.0 and CTR 3 working After some replies here I will post them.....
Click to expand...
Click to collapse
Sagar_Patel said:
....twrp v2.8.1.0 was working absolutely fine (at least for a while!!!) ....however, after using couple of hours ....it was crashed...not even adb reboot recovery worked......
Click to expand...
Click to collapse
have you completed testing? have you got your testers to confirm they're release-worthy?
avi3230 said:
Anyone using TWRP 2.8.1.0 please give feedback.....so that i can post 2.8.2.0.
Click to expand...
Click to collapse
avi3230 said:
.....About TWRP already 70 download and no reply, dont know why??
I already have TWRP 2.8.2.0 and CTR 3 working. After some replies here I will post them......
Click to expand...
Click to collapse
just saw this.
C3C076 said:
I've read somewhere in N5 forums that there's a problem with TWRP 2.8.2.0 regarding reboot to recovery.....
Click to expand...
Click to collapse
anyone on twrp v2.8.2.0 for xolo q3000, please check and report. thanks.
edit: tried 'reboot to recovery'. was able to boot into twrp v2.8.2.0 in several ways. :good:
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
{
"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"
}
MultiROM is one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must NOT be encrypted (hint: if you don't know what it is, then it is encrypted).
To decrypt your device:
Backup ALL your data if you need to recover later (TWRP backup to USB or copy to your PC)
In fastboot mode:
Code:
fastboot format userdata
In TWRP: Flash Magisk (recommended) or SuperSU to avoid auto-encryption in next boot.
MultiROM has 2 parts you need to install:
Modified recovery (TWRP). Flash it as usual TWRP (fastboot flash recovery, or any flasher app if you're rooted).
MultiROM. Install it as usual zip from modded TWRP once flashed.
Go into TWRP MultiRom settings and be sure that "Enable No-KEXEC Workaround" is enabled (enabled by default)
Your current rom will not be erased by the installation.Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 6.x after first boot takes 900+mb of space.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
MIUI ROM as Secondary <--- Latest versions fix this, so you shouldn't need it anymore
Install MIUI as secondary via MultiROM settings in TWRP
Boot into your (rooted) primary
Edit fstab.qcom file in /storage/emulated/multirom/roms//boot/ and add /cache partition entries:
Code:
/dev/block/bootdevice/by-name/cache /cache f2fs nosuid,nodev,noatime,inline_xattr,flush_merge,data_flush wait,check,formattable
/dev/block/bootdevice/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait,check,formattable
Alternatively you can use attached file "fstab.qcom.txt" (rename to: fstab.qcom without .txt ). Be sure to set proper permissions (copy from original fstab.qcom, after renaming to fstab.qcom.bak, don't delete it...)
DON'T FORGET to flash Magisk / SuperSU after flashing to avoid re-encryption if you're flashing stock (not modded).
Known issues
You must wait a few seconds (3-5) before you get touch screen responsiveness in TWRP and MultiROM. (fixed by 2017.08.01 build) -- USUAL WHEN SWITCHING FROM MIUI
Some FCs on some secondary ROMs: Try using multiromfix.zip, thx to @Startrek852 (to disable sdcardfs support in that secondary) -- USE MAGISK 13.5+
Issues with TWRP to boot on 4GB/128GB model... (Working on troubleshooting...) -- PRELIMINARY FIX HERE
Reporting issues
As you surely understand, a simply "it does NOT work" is not enough... so please, report your issue describing scenario as much as you can, try following this (as much as possible information is welcome, it's very tiring for me asking what this, what that, etc...):
Issue description (what, how, when, etc...)
Device model : 4GB or 6GB RAM
Decrypted? /cache and /data FSs ? (We assume IS decrypted becaues you're using MultiROM, and EXT4 FS for /cache and /data if you don't know or manually formatted to F2FS)
TWRP version + MultiROM version
Primary ROM (name, better with version)
Firmware version
Secondary ROM (the one with the issue, name and better version)
Custom kernel ? (name and version if so) <--- In theory, we shouldn't support scenarios with custom kernels.... (they can touch system stuff that make things more complex)
Xposed ? <--- Sorry we DON'T support MultiROM if you use Xposed
Google Apps (name, better with version)
Magisk / SuperSU (version and if you use it in Primary and/or Secondary and version)
Logs <--- This would be amazing great and helpful !!!! (you can get them via adb shell, terminal or using any tool)
*Original post and example in this post, please:
Download
You can download all stuff from here, where you can find latest TWRP and MultiROM. If you need to uninstall MultiROM, you can use this uninstaller.
MultiROM Manager (apk) available here.
Source code
MultiROM - https://github.com/MultiROM-dev/multirom
Modified TWRP - https://github.com/multirom-dev/Team-Win-Recovery-Project
MultiROM device tree - https://github.com/BitOBSessiOn/android_device_xiaomi_lithium
Special thanks to:
@Tasssadar for creating this awesome utility
@nkk71 for the No-KEXEC workaround
@AdrianDC and all MultiROM guys involved in its development
@jcadduono for TWRP port
We will have to try soon... It's the perfect set up for flashaholics
Great news [emoji847][emoji847]
Envoyé de mon MIX en utilisant Tapatalk
I can't make it work
fil0s0f0 said:
I can't make it work
Click to expand...
Click to collapse
The MultiROM app from market is only for official devices (I haven't updated the Android app, imo it's not very useful), So you must follow OP steps.
If you have some issue, please, describe your problem and we will try to help.
Keep in mind that you must have unlocked bootloader, decrypted device, etc...
Device decrypted, bootloader unlocked, and well, there is no instructionbon op but, I figure out and I'll leave my feedback
fil0s0f0 said:
Device decrypted, bootloader unlocked, and well, there is no instructionbon op but, I figure out and I'll leave my feedback
Click to expand...
Click to collapse
Yes, there are, please, revise OP, and describe which steps have you followed to find out what's your issue. Thx
provided TWRP wont boot into it after flash. shows some scrambled image, shows animation with MultiRom image but wont enter recovery
also command: fastboot flash userdata
gives this output
Superb, I missed it in this great smarphone
acasmc said:
provided TWRP wont boot into it after flash. shows some scrambled image, shows animation with MultiRom image but wont enter recovery
also command: fastboot flash userdata
gives this output
Click to expand...
Click to collapse
Sorry:
fastboot format userdata
I correct OP.
The TWRP is tested... I will revise.
BitOBSessiOn said:
Sorry:
fastboot format userdata
I correct OP.
The TWRP is tested... I will revise.
Click to expand...
Click to collapse
could it be, that while I'm encrypted TWRP will not work? flashed it with Rashr and fia Fastboot method. didnt work either way.
acasmc said:
could it be, that while I'm encrypted TWRP will not work? flashed it with Rashr and fia Fastboot method. didnt work either way.
Click to expand...
Click to collapse
Too weird... I've just downloaded and flashed again with rashr and ok.
Which model do you own (128/256)? Primary rom...?
TWRP must work ok with encrypted /data (but you need decrypted for MultiROM).
I'm on latest Miui China Beta Developer ROM (7.7.20), model is 128Gb/4Gb
Mr.Raines TWRP is working fine for me.
acasmc said:
I'm on latest Miui China Beta Developer ROM (7.7.20), model is 128Gb/4Gb
Mr.Raines TWRP is working fine for me.
Click to expand...
Click to collapse
Can you try some of older versions in testing or backup folder in n AFH, please...?
Can you take a photo of error if it still occurs...?
there is only one TWRP in your folder. can you point me to another. I'll try no worries
acasmc said:
there is only one TWRP in your folder. can you point me to another. I'll try no worries
Click to expand...
Click to collapse
You can see /bak and /testing folders here:
https://www.androidfilehost.com/?w=files&flid=201564
Great mod, I was been using Dual boot patcher app to boot into multiple roms(currently 5 roms). Hopefully this mod makes the things easier than before lol. I may give it a go when i feel a fully clean start. Thanks for providing the mod[emoji106]
Konsstantine34 said:
Great mod, I was been using Dual boot patcher app to boot into multiple roms(currently 5 roms). Hopefully this mod makes the things easier than before lol. I may give it a go when i feel a fully clean start. Thanks for providing the mod[emoji106]
Click to expand...
Click to collapse
Usually I don't start to develop for a device before I can use MultiROM....
BitOBSessiOn said:
You can see /bak and /testing folders here:
https://www.androidfilehost.com/?w=files&flid=201564
Click to expand...
Click to collapse
tried other two that are on that link. still the same. sadly don't have another phone with me, to take a picture.
guess gonna have to wait for an update. :/
BitOBSessiOn said:
Note 1: Your device must NOT be encrypted (hint: if you don't know what it is, then it is encrypted).
Click to expand...
Click to collapse
About encrypting, Is it enough to flash the "no-verity-opt-encrypt-5.1".zip?, And if its not, Is there a guide of how to encrypt my device?