Resurrection Remix by quanganh2627
What is NOT working:GPS, FM radio, Autorotation
What is working:Other like Wi-Fi, OTG, baseband and etc.
How to install it:Step 0:
Bootloader unlock is required for every custom rom. You can use this tool for unlock:
https://drive.google.com/file/d/0B-Fin8UxrD6PWTZtR2VXX0dxcU0/view?usp=sharing
Step 1:
You should download files for flashing:
File with RR rom (Resurrection-Remix-LP-v5.5.8-20151024-a500cg.zip):
beta7.1
NOTE: RR builds for Zenfone 5 are compatible with Zenfone 6!
IMPORTANT: Do not forget to flash Xposed with RR Beta7.1. This way many issues (lags, memory bugs) will be solved.
OpenGapps: Download from Google Drive
XPOSED v78 : Download from Google Drive
ADB v1.0.32: Download from Google Drive
TWRP 2.8.7.0 recovery by quanganh2627 (new Decmber build): Download from Google Drive
Step 2:
1) Unpack archive with ADB and put TWRP image there.
2) Copy file with rom and gapps to internal/external memory of your phone.
3) Then you should reboot your phone in the droidboot mode. (turn off you gadget then press Turn off button and volume + button)
Then go to the ADB folder and hold Shift + Right Mouse button and write this command:
Code:
fastboot flash recovery new-zen5-reco.img
Then you should reboot your phone in the recovery mode. (turn off you gadget then press Turn off button and volume - button)
Step 3:
Then you phone will reboot in the recovery. In the recovery you should instal two packages: Resurrection-Remix-LP-v5.5.7-20151012-a500cg.zip and gapps-L-x86-20150816-signed.zip.
NOTE: FlashResurrection-Remix-LP-v5.5.7-20151012-a500cg.zip file first.
Step 4:
After flashing, you should format (not wipe) data and cache in the TWRP.
Then you should reboot to system.
Bug reporting:Attach logcat and detailed describe the issue. Send this to quanganh2627:
http://forum.xda-developers.com/member.php?u=5392204
Credits:to @quanganh2627 @knoneNull @shakalaca and Hazouh
XDA:DevDB Information
Resurrection Remix V5.5.9 for Asus Zenfone 6 by quanganh2627 , ROM for all devices (see above for details)
Contributors
tank0412, dimdimdim
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: unlocked bootloader
Based On: CM 12.1
Version Information
Status: Beta
Current Beta Version: 7.1
Beta Release Date: 2015-12-06
Created 2015-10-18
Last Updated 2015-12-06
To fix camera, you should open build.a600cg.prop and copy all stuff from this file to build.prop file.
And what's wrong with camera? Mine works fine on 5.5.7 kernel 6.6
---------- Post added at 09:47 AM ---------- Previous post was at 09:45 AM ----------
Need help with Xposed. I've got boot loop with x86 sdk22 v74. Xposed for lollipop doesn't flash framework itself.
Okay, seems, the problem with Xposed is solved by flashing XPOSED X86 SDK22 v75 to 6.6 RT BETA http://forum.xda-developers.com/showthread.php?p=63396458#post63396458
some observations on beta with 6.5-6.6 kernels:
- touch freeze after call (system is still up, you can use your hard buttons to practice bringing volume panel and power menu up. by6the way, when I discussed xposed workability on zenfone 6 in my pms, one man mentioned he had same behavior within twrp recovery if flash zenfone 5 twrp on zenfone 6. IDK if this is in any way connected (anyway, we are flashing native zenfone 5 rom and recovery, so, everything is possible), but posting it here for devs, maybe it will bring them some ideas
- 6.6 kernel: burst mode on zenfone camera doesn't work. it starts working normally, but never stops and nothing saves. 6.5 seems works fine.
- Xanwars kernel v2(fixed lags) doesn't start second sim... Taking into account there is no raise in performance for me on this kernel (have no chance to test touch freezes after call due to a not working sim2) even though it allows overclock up to 2.2 and all the governors and schedulers are here.. Staying with beta 6.7 and 6.5 kernel
will update this. it's not a bug report with logcat yet as far as there is nobody here who develops for zenfone 6. yet, I hope.
ROM OS Version:*5.1.1 Lollipop
ROM Kernel:*Linux 3.10.20
Im still using beta6.6 without flashing x anwar kernel, i haven't encounter any lags and freezes, after first boot, reboot the device to twrp and try to install xposed v65,73,74 but it failed and finally succesfully installed on v75, so i think the best way after installing RR is to reboot the device 5 times after the first boot of installing RR. Then use it in 12 hours without installing anything like xposed, then observe and monitor on the performance.
Hajile caz said:
ROM OS Version:*5.1.1 Lollipop
ROM Kernel:*Linux 3.10.20
Im still using beta6.6 without flashing x anwar kernel, i haven't encounter any lags and freezes, after first boot, reboot the device to twrp and try to install xposed v65,73,74 but it failed and finally succesfully installed on v75, so i think the best way after installing RR is to reboot the device 5 times after the first boot of installing RR. Then use it in 12 hours without installing anything like xposed, then observe and monitor on the performance.
Click to expand...
Click to collapse
You don't have touch freezes after call on 6.6?
What about burst mode on asus camera? Does it work on your phone?
Which AnTuTu score do you get on 6.6?
Max what I saw on any kernel was 28900
Btw, dpi change on 6.2 kernel gives me boot loop. 6.7&6.5 both work fine.
I haven't experience freezing on calls, both incoming and outgoing calls, btw I have unlocked my bootloader from downgrading to Jellybean firmware and use the official unlocker tool from Asus.
My asus camera is working, burst mode is also working, After my first boot of RR, i have copy the a600cg build prod to both a501cg and the file build prop which i believe for a500cg, I also asked my friend, to share the media_profiles.xml from stock lollipop, and then i push it to system/etc and set permission to octal.
I have not try to flash the kernel from 6.2.
My antutu score when i was on 6.5 is 20k while after dirty flashing 6.6 it gave me 27k without flashing any kernel
My antutu score on beta6.6 without flashing any kernel
nice rom, so much faster i love it !!! recommend
my deepsleep not working at 6.7 i using 6.5 kernel and will try another
aymanz said:
nice rom, so much faster i love it !!! recommend
my deepsleep not working at 6.7 i using 6.5 kernel and will try another
Click to expand...
Click to collapse
I have not ever had any issues with deep sleep on any kernel and with no tricks or hacks. I believe it's because of some hick ups in old data or cache.
---------- Post added at 07:08 PM ---------- Previous post was at 06:58 PM ----------
Hajile caz said:
I haven't experience freezing on calls, both incoming and outgoing calls, btw I have unlocked my bootloader from downgrading to Jellybean firmware and use the official unlocker tool from Asus.
My asus camera is working, burst mode is also working, After my first boot of RR, i have copy the a600cg build prod to both a501cg and the file build prop which i believe for a500cg, I also asked my friend, to share the media_profiles.xml from stock lollipop, and then i push it to system/etc and set permission to octal.
I have not try to flash the kernel from 6.2.
My antutu score when i was on 6.5 is 20k while after dirty flashing 6.6 it gave me 27k without flashing any kernel
Click to expand...
Click to collapse
So, you do believe most of the bugs come from the not completely proper bootloader unlock? If you know more details, that would be great if you can share, it's interesting.
dimdimdim said:
I have not ever had any issues with deep sleep on any kernel and with no tricks or hacks. I believe it's because of some hick ups in old data or cache.
---------- Post added at 07:08 PM ---------- Previous post was at 06:58 PM ----------
So, you do believe most of the bugs come from the not completely proper bootloader unlock? If you know more details, that would be great if you can share, it's interesting.
Click to expand...
Click to collapse
In my own experience, I think that the best way to unlock the bootloader on our device is by using the official unlocker from Asus. Im always checking the forum here regarding RR, and i've noticed that the most mentioned topic is the screen freezes, which doesn't happen to me. Most of the users unlocked their BL from stock LP by flashing the dnx and ifwi files. And those users suffered from a massive lags and freezes. I have installed cm12.1 before i move to RR. When i was on cyanogenmod, i didn't experience any freezing issue. Due to my curiosity, i tried to downgrade to JB, then manual update to KK with bridge update then upgrade to LP. From stock LP, i flashed dnx and ifwi to unlock my Bootloader, then flashed cm12.1. After my first boot, im exploring my new installed rom, then suddenly my screen got frozen.
Hajile caz said:
In my own experience, I think that the best way to unlock the bootloader on our device is by using the official unlocker from Asus. Im always checking the forum here regarding RR, and i've noticed that the most mentioned topic is the screen freezes, which doesn't happen to me. Most of the users unlocked their BL from stock LP by flashing the dnx and ifwi files. And those users suffered from a massive lags and freezes. I have installed cm12.1 before i move to RR. When i was on cyanogenmod, i didn't experience any freezing issue. Due to my curiosity, i tried to downgrade to JB, then manual update to KK with bridge update then upgrade to LP. From stock LP, i flashed dnx and ifwi to unlock my Bootloader, then flashed cm12.1. After my first boot, im exploring my new installed rom, then suddenly my screen got frozen.
Click to expand...
Click to collapse
Do you think it will help for those, who have their bootloader unlocked unofficially, to lock it again and unlock with asus unlock?
I think it might be helpful for those devices that suffered from lags and freezes. Although it's a long process, but why not gave it a shot then, we all came this far.
beta 6.8 boots well http://forum.xda-developers.com/showpost.php?p=63457490&postcount=1918 on zenfone 6
first observations:
- no vibro (but this is common) -fixed the build from 24.10
- dpi change goes in some strange way: it works, but at starting apps point gets boot loop. anyway, you can break the loop forcing power off with hardware button at this point and bring it back to boot, which goes normally this way and never gets into the loop again after.
..still testing, got it in the night..
kloroform said:
thank you, downloading the ROM now, but my question is how stable is the ROM is now? Can I use all the ASUS apps with this ROM, the asus camera app mainly. Is it possible?
And can I come back to asus stock rom if I wish? I already made a backup, but a youtube channel guy on youtube told me few weeks back that it depends on the rom, he was talking about some odex-deodex thing. And if my ROM is odexed it wont boot even if I restore my stock rom backup on the same phone?
Click to expand...
Click to collapse
The rom is stable just as it is for zenfone 5. I'm using it after stock lollipop as a daily driver with hard use.
I don't know about every asus rom, but the developer includes the most usable asus apps in the rom. Remember, it's the resurrection rom for asus zenfone specifically?
The camera works fine. For me a burst mode doesn't work, but other people say it works well. I'd recommend to unlock bootloader with asus stock unlock tool in order to have less bugs.
From what I know you should go with dirty flash (no wipes before the flash process) over LP stock. See complete procedure in op.
If your rom is just stock with no modifications to the system, then it should flash fine from what I know.
But anyway, you do it all at your own risk, as always.
dimdimdim said:
The rom is stable just as it is for zenfone 5. I'm using it after stock lollipop as a daily driver with hard use.
I don't know about every asus rom, but the developer includes the most usable asus apps in the rom. Remember, it's the resurrection rom for asus zenfone specifically?
The camera works fine. For me a burst mode doesn't work, but other people say it works well. I'd recommend to unlock bootloader with asus stock unlock tool in order to have less bugs.
From what I know you should go with dirty flash (no wipes before the flash process) over LP stock. See complete procedure in op.
If your rom is just stock with no modifications to the system, then it should flash fine from what I know.
But anyway, you do it all at your own risk, as always.
Click to expand...
Click to collapse
thanks for answering my questions.
yes I have unlocked bootloader but not with the Asus's official tool. So, shall I use that tool to lock the bootloader again and then use Asus's unlock tool?
kloroform said:
thanks for answering my questions.
yes I have unlocked bootloader but not with the Asus's official tool. So, shall I use that tool to lock the bootloader again and then use Asus's unlock tool?
Click to expand...
Click to collapse
I'd like to help you, man, but I know nothing about bootloader unlock nuances on zenfone. Everything I know, I said: my burst mode on asus camera doesn't work and I have screen freezes with kernels older, than 6.2, and a man in this thread, you can check previous posts, has no these issues and he (and many others) believes it has connection to the bootloader unlock method.
Just be careful and make your decision, as playing with a bootloader lock/unlock with different tools could be dangerous. Remember, I know nothing about this.
@dimdimdim
I just dirty flashed RR 5.5.8, I have'nt flash a custom kernel, as I was confused which is the best kernel for this build, can you share which kernel did you flashed? Thanks
Hajile caz said:
@dimdimdim
I just dirty flashed RR 5.5.8, I have'nt flash a custom kernel, as I was confused which is the best kernel for this build, can you share which kernel did you flashed? Thanks
Click to expand...
Click to collapse
Hello, I'm using default one. Everything is ok with it for me, besides known bugs which are still here: screen freezes, gps, no screen rotation.
Related
Yet another custom rom with the latest Android Operating System Marshmallow for Lenovo A6000 and Plus users. It
is unnoffcial but it comprises the latest updates of Marshmallow and CM 13. The custom rom is still under beta phase testing and there might be lots of bugs and instability. We would advice you to flash this custom rom if you’re not using as the primary device. You
can test the features of Marshmallow on your Lenovo A6000 but there might be errors or performance issues. The Lenovo A6000 CM 13 Marshmallow ROM is only 400 MB and it needs to be installed on a Lollipop based rom already with the TWRP custom recovery.
DISCLAIMER : Rooting or flashing custom roms results breaking the warranty of the device. Techolaty and its authors are not responsible for any damage which is incurred in the process of flashing custom roms or rooting the device. We highly advice to take a backup of your device prior to performing the process.
Pre-Requisites
Lollipop pre-installed
TWRP Custom Recovery – Read the guide from here
http://www.techolaty.com/install-twrp-recovery-on-lenovo-a6000-lollipop/
Lenovo A6000 CM 13 Marshmallow ROM – Download it from here
https://drive.google.com/file/d/0B3az2bvjmHEyeXhSS3BTcGtnaTg/view
GApps 5.1.x – Download it from here
http://www.mediafire.com/?1fjikny9l32an9m
About The Rom
Android Verion : 6.0
ROM Version : 1.0 Beta
Type : Cyanogenmod 13
Author/Credits : FlourMo
Features
Google Now on Tap
App permissions
Battery optimisation
Most used apps
Doze
Automatic backup and restore
Manage volumes more intuitively
Select text more accurately
Also check - Lenovo A6000 AOSP 5.1 Custom ROM
How to Install
Step 1 : Copy the CM 13 Marshmallow ROM and GApps in your SD card
Step 2 : Boot into Recovery
Switch off your device
Now press Volume Down + Power Button together for 2-5 seconds until you see the bootloader
Connect the USB to your PC/Laptop and then flash TWRP recovery (read the guide here)
Step 3 : Make full wipe including “system” (data, dalvik, system, cache)
Step 4 : Now go back and click install and then click one level up
Step 5 : Flash the ROM
Step 6 : Reboot (the first boot can take up to 2-5 minutes)
Bugs
FM not working
GPS Positioning not accurate
sourav8434 said:
Yet another custom rom with the latest Android Operating System Marshmallow for Lenovo A6000 and Plus users. It
is unnoffcial but it comprises the latest updates of Marshmallow and CM 13. The custom rom is still under beta phase testing and there might be lots of bugs and instability. We would advice you to flash this custom rom if you’re not using as the primary device. You
can test the features of Marshmallow on your Lenovo A6000 but there might be errors or performance issues. The Lenovo A6000 CM 13 Marshmallow ROM is only 400 MB and it needs to be installed on a Lollipop based rom already with the TWRP custom recovery.
DISCLAIMER : Rooting or flashing custom roms results breaking the warranty of the device. Techolaty and its authors are not responsible for any damage which is incurred in the process of flashing custom roms or rooting the device. We highly advice to take a backup of your device prior to performing the process.
Pre-Requisites
Lollipop pre-installed
TWRP Custom Recovery – Read the guide from here
http://www.techolaty.com/install-twrp-recovery-on-lenovo-a6000-lollipop/
Lenovo A6000 CM 13 Marshmallow ROM – Download it from here
https://drive.google.com/file/d/0B3az2bvjmHEyeXhSS3BTcGtnaTg/view
GApps 5.1.x – Download it from here
http://www.mediafire.com/?1fjikny9l32an9m
About The Rom
Android Verion : 6.0
ROM Version : 1.0 Beta
Type : Cyanogenmod 13
Author/Credits : FlourMo
Features
Google Now on Tap
App permissions
Battery optimisation
Most used apps
Doze
Automatic backup and restore
Manage volumes more intuitively
Select text more accurately
Also check - Lenovo A6000 AOSP 5.1 Custom ROM
How to Install
Step 1 : Copy the CM 13 Marshmallow ROM and GApps in your SD card
Step 2 : Boot into Recovery
Switch off your device
Now press Volume Down + Power Button together for 2-5 seconds until you see the bootloader
Connect the USB to your PC/Laptop and then flash TWRP recovery (read the guide here)
Step 3 : Make full wipe including “system” (data, dalvik, system, cache)
Step 4 : Now go back and click install and then click one level up
Step 5 : Flash the ROM
Step 6 : Reboot (the first boot can take up to 2-5 minutes)
Bugs
FM not working
GPS Positioning not accurate
Click to expand...
Click to collapse
screenshots plz
I am looking for one.. Thanks for posting.. I really like Flourmo ROMs
Sent from my Lenovo K30-T using Tapatalk
Anybody managed to flash cm13 in 6k+
Sent from my Lenovo using XDA Free mobile app
Yep. I donno if its my prob or os. the phone keeps rebooting after installing this os. so proceed with caution.
Its in beta version may have several bugs. Is it rebooting automatically? Hows the batery backup
Sent from my Lenovo using XDA Free mobile app
I suggest No One to try this CM 13 ROM..I have tried to install it multiple times & Everytime my A6000 was stuck at bootloop...
I was using Mokee ROM (Lollipo 5.1.1) & wiped Dalvik,Cache,System & data & installed Cm 13 & gapps 5.1.1 successfully..But When I boot up,it is stuck at Lenovo Logo Screen (Bootscreen) .I have waited for more than 15 minutes to bootup ,but it didn't happen..
So I request you to proceed with caution & do not install it..Wait for the second version or other marshmallow ROMs
averagegeek said:
I suggest No One to try this CM 13 ROM..I have tried to install it multiple times & Everytime my A6000 was stuck at bootloop...
I was using Mokee ROM (Lollipo 5.1.1) & wiped Dalvik,Cache,System & data & installed Cm 13 & gapps 5.1.1 successfully..But When I boot up,it is stuck at Lenovo Logo Screen (Bootscreen) .I have waited for more than 15 minutes to bootup ,but it didn't happen..
So I request you to proceed with caution & do not install it..Wait for the second version or other marshmallow ROMs
Click to expand...
Click to collapse
See the update-script it doesnt even flash the rom. i will update the proper update script later. try and u ll get it boot up
rahulsnair said:
See the update-script it doesnt even flash the rom. i will update the proper update script later. try and u ll get it boot up
Click to expand...
Click to collapse
After trying the Cm13 Rom with no luck,I have restored the TWRP backup of my previous ROM..After REBOOT,the Screen doesn't turn ON & the Phone keeps vibrating ..Does my phone turn into a Hard Brick?
Can You help?
averagegeek said:
After trying the Cm13 Rom with no luck,I have restored the TWRP backup of my previous ROM..After REBOOT,the Screen doesn't turn ON & the Phone keeps vibrating ..Does my phone turn into a Hard Brick?
Can You help?
Click to expand...
Click to collapse
is your phone detected by system if you connect to pc?
averagegeek said:
After trying the Cm13 Rom with no luck,I have restored the TWRP backup of my previous ROM..After REBOOT,the Screen doesn't turn ON & the Phone keeps vibrating ..Does my phone turn into a Hard Brick?
Can You help?
Click to expand...
Click to collapse
Flash the stock lollipop firmware which was 1 gb in size from Twrp. Just copy it into your Sd and flash it directly.
averagegeek said:
After trying the Cm13 Rom with no luck,I have restored the TWRP backup of my previous ROM..After REBOOT,the Screen doesn't turn ON & the Phone keeps vibrating ..Does my phone turn into a Hard Brick?
Can You help?
Click to expand...
Click to collapse
are you able to fastboot !! or get into reccovery!!
abhifx said:
is your phone detected by system if you connect to pc?
Click to expand...
Click to collapse
No...It keeps on vibrating when connected to PC or Power Adapter with Nothing on Display ..I have manually remove the battery to stop the Vibration
---------- Post added at 11:07 AM ---------- Previous post was at 11:05 AM ----------
zeon321 said:
Flash the stock lollipop firmware which was 1 gb in size from Twrp. Just copy it into your Sd and flash it directly.
Click to expand...
Click to collapse
My Phone doesn't get detected in my PC..Fastboot is not working...Display is not Powering On..Then how am I supposed to flash the Stock Firmware?
---------- Post added at 11:10 AM ---------- Previous post was at 11:07 AM ----------
rahulsnair said:
are you able to fastboot !! or get into reccovery!!
Click to expand...
Click to collapse
Nope...It keeps on vibrating..No fastboot...No Display...No connection with my PC....
Did you tried the volume up+ powerbutton combination to enter onto boot loader
Sent from my Lenovo using XDA Free mobile app
ajithvs126 said:
Did you tried the volume up+ powerbutton combination to enter onto boot loader
Sent from my Lenovo using XDA Free mobile app
Click to expand...
Click to collapse
Yup..No response ..It keeps vibrating
No lenovo logo..?
Sry bro i dont know what to do unless getting it into the bootloader
Sent from my Lenovo using XDA Free mobile app
You guys need to flash the stock lollipop, then flash CM12.1 and then CM 13. Worked for me. Try it yourself.
For few days ,I have tried to unbrick my A6000 with No Luck.So I have to visit the Service Center & they replaced the Motherboard to fix my phone.I doubt a "wrong boot partition Restore" have caused the issue.What's your thoughts on that?
VeerAmrit said:
You guys need to flash the stock lollipop, then flash CM12.1 and then CM 13. Worked for me. Try it yourself.
Click to expand...
Click to collapse
screen shots plz...
vardhan21 said:
screen shots plz...
Click to expand...
Click to collapse
Check the video instead - https://www.youtube.com/watch?v=7Uzwi3jsmE0
Okay so here's the info to the best of my knowledge,
Phone Model : Moto G 3rd Gen (XT1550, dual sim, 2gb RAM, 16gb ROM, India)
Bootloader Status : Unlocked
Root Status : Rooted
Recovery : Stock
ROM : Stock ROM 5.1.1
I've been running the stock Recovery & ROM with high hopes of getting an official OTA Marshamallow update.
To truly customize the device to my liking I flashed the xposed framework (the arm version) , it worked fine and all the modules I installed worked perfectly.
I also had Device Control, Xposed Gels, and some other apps to bring my Stock ROM experience close to that of Cyanogen MOD.
When the OTA Marshmallow update started rolling in , I was unable to install the update even after successfully downloading the file numerous times. But i was so comfortable with my device and all the customization I had on my device that I decided to keep using my customized Stock ROM.
4 months later (now) the lack of a gyro in this device and my eagerness to get into VR headsets has left me with no choice but to sell it and get another phone. So i needed it in a sale worthy condition, without the customization and with the Marshmallow update installed.
I uninstalled the xposed framework and all the modules but was still unable to install the OTA update.
So i figured i'd install CyanogenMOD with TWRP custom recovery.
I have done this for quiet a lot of my friends and am fairly used to the steps involved. I use the " minimalADB fastboot " kit and my device on fastboot to flash recovery. For some reason i was not able to flash the lastest TWRP image (twrp-osprey-3.0.0-r2.img ) for the device nor was i able to boot from it :crying:. The fastboot command prompt on my PC would show success but the devices would not restart into the custom recovery like it is supposed to, but the device would stay at the fastboot mode and kept restarting everytime i selected the recovery mode option.
I had an older image (twrp-osprey-2.8.7-r3.img ) which i couldn't flash either but i was able to boot into TWRP with this image. From here i tried installing the latest CM12.1 nightly available (cm-12.1-20160227-NIGHTLY-osprey.zip) as soon as i swiped the device would just reboot, i tried this numerous times and with other nightly builds as well.
In haste and frustration i wiped the cache/dalvik , internal storage and system through TWRP , thinking that changes made in the quest of customizing my device were causing this hindrance. I had no OS now. I went over trying to flash TWRP and CM12.1 many times again with the same issues.
I came about a thread on How to " Fastboot Flash Moto G (3rd Gen) Factory Firmware Images " (http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750) & used this firmware image " Retail Asia | India (2GB) - XT1550_OSPREY_RETASIA_DS_2GB_6.0_MPI24.65-25_cid7 ". Still no progress.
The bootloader unlocked warning has come back (i flashed a stock MOTO logo there earlier) which keeps flashing on my screen again and again , no booting into OS or anything else. Not even an error. As if there is no OS installed.
I have gone about the procedure in the above thread a couple of times, with no success and the same problem.
Is there any reason why i'm unable to flash a custom recovery or ROM ??? What am i missing???
Please help i'm stuck, pulling my hair out with no phone and completely frustrated.
Thanks in advance.
Did you check your build no for stock ROM?
samirza692 said:
Did you check your build no for stock ROM?
Click to expand...
Click to collapse
Nope. Too late for that now.
If you're asking in regard to the stock firmware I tried to flash, it didnt depend on the build number. Just the model number and the RAM.
ashrith.s said:
Nope. Too late for that now.
If you're asking in regard to the stock firmware I tried to flash, it didnt depend on the build number. Just the model number and the RAM.
Click to expand...
Click to collapse
okay i am not a developer nor a noop but trying to help you
try to flash stock rom from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 but dont mistake this time double check your model with build number using carefuly the steps from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
You will not brick the phone if you use the latest firmware and do a factory reset before flashing.
Good luck.
but do at your own risk i am not responsible for anything
samirza692 said:
okay i am not a developer nor a noop but trying to help you
try to flash stock rom from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 but dont mistake this time double check your model with build number using carefuly the steps from here http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
You will not brick the phone if you use the latest firmware and do a factory reset before flashing.
Good luck.
but do at your own risk i am not responsible for anything
Click to expand...
Click to collapse
the link provided is the exact same link from where I flashed a stock rom before.
build number for stock rom??? am i missing something???
all i see is the model variant (xt1550 is my phone)
RAM specification (mine is 2gb)
and the region (mine is retails asia | india )
so i went with the following firmware
Retail Asia | India (2GB) - XT1550_OSPREY_RETASIA_DS_2GB_6.0_MPI24.65-25_cid7
where does the build number come into the equation???
Please lemme know if im doing something wrong. Thanks for the replies.
So I've successfully flashed twrp-osprey-2.8.7-r3.img to my device and I've been able to boot into twrp. The touchscreen doesn't seem to respond though. It asks to swipe to begin and I'm stuck again.
I had the screen replaced a couple of days ago.
Could it be a faulty screen or a software issue?
P.S. I have not been able to flash any version of twrp after the above mentioned version (v 3.0.0 is the latest stable version) but the ones prior are flashable.
Hey, contact me via PM and il do my best to help you in this.
therealduff1 said:
Hey, contact me via PM and il do my best to help you in this.
Click to expand...
Click to collapse
Is not big issue
Is it still possible to boot back into the OS? If it is, check if you have OEM unlocking enabled, since you're on stock ROM, it might be gotten unchecked after unlocking your bootloader because that's what happened with me. If you do t wether or not that was checked, you're at a dead end and there's nothing you can do. You can try paying someone to fix it, i.e., Motorola.
My Mi 4c arrived yesterday. I bought it using donations that I received from various project (Samsung Galaxy Tab 2, Tab 3, Tab 4, OnePlus One, Xiaomi Redmi 2). It's seems for Chinese market: a lot of Chinese apps, incomplete English translation, no Google services. Fortunately, TWRP port already available for this device, so rooting and installing GApps is easy. Somehow I still want to keep the original recovery.
1. Boot to fastboot mode (VOL DOWN + POWER) to fastboot TWRP:
Code:
fastboot boot twrp.img
2. Flash SuperSU in TWRP
3. Flash Open GApps nano in TWRP
As you know, loading touchscreen firmware need times in TWRP. Just do other thing while waiting for it :laugh: The possible cause is firmware "ping-pong" issue when in kernel touchscreen firmware different between recovery and normal boot. But why loading a firmware so that long?
My device come with MIUI 7.1.4.0, unlocked bootloader. I just upgrade it to 7.2.1.0 without firmware update to keep the bootloader unlocked but use 7.1.6.0 kernel to boot it because no go with the new kernel (incompatible firmware?), MIUI logo forever. BEWARE: Don't upgrade your device to 7.2.1.0 using a standard method, your bootloader will be locked!
Attached Hardware Info report for my future reference if I decide to develop custom ROM/kernel.
@emfox, I'm with you :laugh:
MIUI 7.2.1.0 without firmware update.
how can you update to 7.2.1.0 version without firmware update?
btw, I think I will wait for Xiaomi EU or sMIUI, so I can flash them via twrp....
tuanhung303 said:
how can you update to 7.2.1.0 version without firmware update?
btw, I think I will wait for Xiaomi EU or sMIUI, so I can flash them via twrp....
Click to expand...
Click to collapse
Backup /system/lib/modules, download 7.2.1.0, inject a modified updater-script, flash it in TWRP recovery, restore /system/lib/modules, reflash SuperSU, reflash GApps.
I hope you can make modified rom 7.2.1.0 without bootloader.
ahmaman said:
I hope you can make modified rom 7.2.1.0 without bootloader.
Click to expand...
Click to collapse
Uploading a big file always a problem for me. Maybe I'll create a proper instructions and script for it.
I confirm touchscreen "ping-pong" issue the source problem of TWRP touchscreen freeze on boot. If touchscreen driver found a different firmware version, it will flash a "proper" firmware and delayed touchscreen event initialization.
welcome aboard, my dear friend!
Looks to me, we got another developer. Good
ketut.kumajaya said:
Backup /system/lib/modules, download 7.2.1.0, inject a modified updater-script, flash it in TWRP recovery, restore /system/lib/modules, reflash SuperSU, reflash GApps.
Click to expand...
Click to collapse
omg... is that English? (j/k)
btw, welcome onboard , Xiaomi will release some kernel sources soon, looks like we will have more stable rom in future :laugh:
ketut.kumajaya said:
Uploading a big file always a problem for me. Maybe I'll create a proper instructions and script for it.
I confirm touchscreen "ping-pong" issue the source problem of TWRP touchscreen freeze on boot. If touchscreen driver found a different firmware version, it will flash a "proper" firmware and delayed touchscreen event initialization.
Click to expand...
Click to collapse
Thanks for documenting your findings.
I can tell you I've never experienced the touchscreen bug since day one, I flashed Team Superluminal's TWRP 2.8.7.3 and I can press all buttons soon as I see them
Logic_ said:
Thanks for documenting your findings.
I can tell you I've never experienced the touchscreen bug since day one, I flashed Team Superluminal's TWRP 2.8.7.3 and I can press all buttons soon as I see them
Click to expand...
Click to collapse
yes, the version 2.8 does not have that bug, the version 3.0.0.2 has
Happy to see Indonesian Developer who will contribute in Mi4C Section. really want to meet you in person if have any chance.
Greeting from Indonesia!
wind99 said:
Happy to see Indonesian Developer who will contribute in Mi4C Section. really want to meet you in person if have any chance.
Greeting from Indonesia!
Click to expand...
Click to collapse
Still slowly check Xiaomi changes line by line https://github.com/kumajaya/android_kernel_xiaomi_msm8992/commits/libra-l-oss-kumajaya :laugh:
Hi Guys,
Got my Mi4c unlocked and rooted running cm14 however, when I try and flash an MIUI 8 rom via TWRP the device goes into a bootloop.
I am new to Xiamoi devices (Nexus user) am I missing something? Is there a patch to flash after a rom to prevent bricking?
I'd really like to try MIUI again but don't want to go through the hassle of unbricking my device and reflashing/rooting it.
Many thanks!
p.s Does MIUI 8/CM14 support f2fs?
You have to flash Developer version of the rom which is not out yet. The otherwise-rom package will always lock your bootloader and wont let u access the recovery after (thats why bootloop). CM14 supports F2FS, MIUI8 is still upon the old ext4.
I have the same brick as yours for now and I'm downloading the old 6.12.8 developer version bootloader flashable file to get out of this mess. MIUI is nothing fascinating and they break something with every new update. I'll go back to MOKEE until Android 7 gets stable enough.
dark_prince said:
You have to flash Developer version of the rom which is not out yet. The otherwise-rom package will always lock your bootloader and wont let u access the recovery after (thats why bootloop). CM14 supports F2FS, MIUI8 is still upon the old ext4.
I have the same brick as yours for now and I'm downloading the old 6.12.8 developer version bootloader flashable file to get out of this mess. MIUI is nothing fascinating and they break something with every new update. I'll go back to MOKEE until Android 7 gets stable enough.
Click to expand...
Click to collapse
Thanks for your reply. That surprises me that there still isn't an miui 8 developer ROM out yet for this device. Probably shall never come in that case.
Good to hear that f2fs is supported by cm14 though. Will certainly be running this once I receive my new cases to replace the girly pink cover my mi4c currently houses
danbrown162 said:
Hi Guys,
Got my Mi4c unlocked and rooted running cm14 however, when I try and flash an MIUI 8 rom via TWRP the device goes into a bootloop.
I am new to Xiamoi devices (Nexus user) am I missing something? Is there a patch to flash after a rom to prevent bricking?
I'd really like to try MIUI again but don't want to go through the hassle of unbricking my device and reflashing/rooting it.
Many thanks!
p.s Does MIUI 8/CM14 support f2fs?
Click to expand...
Click to collapse
Just flash miui 8 from xiaomi.eu ones. It supports flashing via twrp.
the development for honor 6x and oreo gsi roms is stopped but only phusson is keep developing oreo gsi rom aosp 8.1 v31. last update was may 3 2019. he did a great job our device. os is complete pure stock,battery backup is amazing and he fixed battery charging speed now device will charge at the speed of stock.
there is two types of firmwares available one is with gapps and root other is without gapps and no root.
first i have tried with gapps version there is no bugs. the only bug is headphones without mic is not detecting. lesser audio switch apk solved that problem.
then i have flased the one without gapps. which is amazing. phone works at its peaks performance, charges faster and drains slower. fingerprint navigation is also improved like if we swipe down it shows notification pannel if we do swipe down again it will expand notification pannel and phone complete navigation can be controlled.
i have flashed cyclox kernel and did over clock for pubg. now pubg runs with smoothes equalls to iphone. i have never got pubg this much smooth, easily wiped out a squad with 7 kills.
without gapps version themed like kitkat and it performance like we are using kitkat on our device.
RAM management is also excellent. it can keep more apps in the memory without killing them.
if we want our device to keep receive google security updates with stable os this is best option.
Download link: https://github.com/phhusson/treble_experimentations/releases/tag/v31
click on assets to get download links.
Can't unlock bootloader
Hi.. My bootloader is locked and honor has closed their official bootloader unlocking service. So what should I do to unlock bootloader unofficially..?
[email protected] said:
Hi.. My bootloader is locked and honor has closed their official bootloader unlocking service. So what should I do to unlock bootloader unofficially..?
Click to expand...
Click to collapse
you need buy dc unlocker to unlock bootloader.
i don't any unofficially ways except this one.
https://forum.xda-developers.com/honor-6x/how-to/guide-unbrick-honor6x-boot-fastboot-t3904381
but this is very risky. i think in this guide we flash stock rom via dload so you bootloader will lock again.
before flashing stock rom this board software install emui 2.0 on honor 6x. with unlocked frp and bootloader. at this point if we managed to get twrp then we can install emui 5 or emui 8 via huru. huru doesn't lock bootloader so we can flash gsi roms. but the problem is we don't have twrp designed for emui 2.0
Ramesh006 said:
you need buy dc unlocker to unlock bootloader.
i don't any unofficially ways except this one.
https://forum.xda-developers.com/honor-6x/how-to/guide-unbrick-honor6x-boot-fastboot-t3904381
but this is very risky. i think in this guide we flash stock rom via dload so you bootloader will lock again.
before flashing stock rom this board software install emui 2.0 on honor 6x. with unlocked frp and bootloader. at this point if we managed to get twrp then we can install emui 5 or emui 8 via huru. huru doesn't lock bootloader so we can flash gsi roms. but the problem is we don't have twrp designed for emui 2.0
Click to expand...
Click to collapse
Thanks for this. Some people say that DC unlocker is Risky. I also had mailed honor about this. Here's what they replied. So should i do it or not..
{
"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"
}
[email protected] said:
Thanks for this. Some people say that DC unlocker is Risky. I also had mailed honor about this. Here's what they replied. So should i do it or not..
Click to expand...
Click to collapse
Give it a try. if you are lucky you will get bootloader unlock for free.
Dc unlocker is safe. i have used it two times to unbrick my device. without any knowledge about dc unlocker I have managed to repair my device within 1 hour. we need buy hcu client for honor devices.
Ramesh006 said:
the development for honor 6x and oreo gsi roms is stopped but only phusson is keep developing oreo gsi rom aosp 8.1 v31. last update was may 3 2019. he did a great job our device. os is complete pure stock,battery backup is amazing and he fixed battery charging speed now device will charge at the speed of stock.
there is two types of firmwares available one is with gapps and root other is without gapps and no root.
first i have tried with gapps version there is no bugs. the only bug is headphones without mic is not detecting. lesser audio switch apk solved that problem.
then i have flased the one without gapps. which is amazing. phone works at its peaks performance, charges faster and drains slower. fingerprint navigation is also improved like if we swipe down it shows notification pannel if we do swipe down again it will expand notification pannel and phone complete navigation can be controlled.
i have flashed cyclox kernel and did over clock for pubg. now pubg runs with smoothes equalls to iphone. i have never got pubg this much smooth, easily wiped out a squad with 7 kills.
without gapps version themed like kitkat and it performance like we are using kitkat on our device.
RAM management is also excellent. it can keep more apps in the memory without killing them.
if we want our device to keep receive google security updates with stable os this is best option.
Download link: https://github.com/phhusson/treble_experimentations/releases/tag/v31
click on assets to get download links.
Click to expand...
Click to collapse
Hi Ramesh006,
thanks for this info. Very excited!
I've some (no, a lot ) questions before try it:
- The correct image for the Honor 6X is this one: system-arm64-aonly-gapps-su.img.xz?
- The root type is Magisk o SuperSU?
- Have you flashed the rom by fastboot or recovery? And in that case, what recovery, Twrp V2 from Elemental thread? Sadly this recovery can't see encrypted partitions :/
- Do I have back to OREO stock or can I flash from another GSI rom?
Thanks again for information sharing!
cheers!
spiritwashere said:
Hi Ramesh006,
thanks for this info. Very excited!
I've some (no, a lot ) questions before try it:
- The correct image for the Honor 6X is this one: system-arm64-aonly-gapps-su.img.xz?
- The root type is Magisk o SuperSU?
- Have you flashed the rom by fastboot or recovery? And in that case, what recovery, Twrp V2 from Elemental thread? Sadly this recovery can't see encrypted partitions :/
- Do I have back to OREO stock or can I flash from another GSI rom?
Thanks again for information sharing!
cheers!
Click to expand...
Click to collapse
Yes arm 64 a only. you can use with gapps or without gapps.
Root is magisk.
i have flashed it via fastboot.
you can flash from other gsi rom but you need to do factory reset via stock recovery after flashing.
after factory reset i have flashed elemental v2 twrp recovery.
im using arm 64 a only without gapps and su so i have flased magisk 19.1 via twrp and it was working.
then i have flashed p20pro hauwei stock camera via twrp and it was working.
Link for camera
https://forum.xda-developers.com/hu...uawei-p20-pro-camera-app-treble-roms-t3798767
then i have flashed james dsp via magisk which is almost looks like viper4android and working.
substratum theme engine works superb we can add or remove any theme without any problems.
titanium backup is not working so we can use oandbackup. which free and work as same as titanium backup.
standby time is great overnight drain is only 1%
finally every month we receive new security updates.
Ramesh006 said:
Yes arm 64 a only. you can use with gapps or without gapps.
Root is magisk.
i have flashed it via fastboot.
you can flash from other gsi rom but you need to do factory reset via stock recovery after flashing.
after factory reset i have flashed elemental v2 twrp recovery.
im using arm 64 a only without gapps and su so i have flased magisk 19.1 via twrp and it was working.
then i have flashed p20pro hauwei stock camera via twrp and it was working.
Link for camera
https://forum.xda-developers.com/hu...uawei-p20-pro-camera-app-treble-roms-t3798767
then i have flashed james dsp via magisk which is almost looks like viper4android and working.
substratum theme engine works superb we can add or remove any theme without any problems.
titanium backup is not working so we can use oandbackup. which free and work as same as titanium backup.
standby time is great overnight drain is only 1%
finally every month we receive new security updates.
Click to expand...
Click to collapse
Sounds good!
Do I have to flash stock recovery before flashing gsi or flashing the system image do the job?
Tomorrow, time permitting, I will try to flash this great work!
Thanks again for info.
spiritwashere said:
Sounds good!
Do I have to flash stock recovery before flashing gsi or flashing the system image do the job?
Tomorrow, time permitting, I will try to flash this great work!
Thanks again for info.
Click to expand...
Click to collapse
you have to manually flash stock recovery. you can flash it anytime before or after flashing os. system don't flash stock recovery.
Ramesh006 said:
you have to manually flash stock recovery. you can flash it anytime before or after flashing os. system don't flash stock recovery.
Click to expand...
Click to collapse
Thanks!
Hello,
My 6x (BLN AL20) has unlocked bootloader and Is actually running PixysOs which is discontinued and actually has no BT working (switching loc. services off won't help in connecting my smartwatch).
Is BT working with this Rom?
Any tutorial on how to proceed for flashing this rom starting from an unlocked device with PyxyOs and Askuccio's TWRP?
Thanks in advance.
Andrea.
Sephiroth79 said:
Hello,
My 6x (BLN AL20) has unlocked bootloader and Is actually running PixysOs which is discontinued and actually has no BT working (switching loc. services off won't help in connecting my smartwatch).
Is BT working with this Rom?
Any tutorial on how to proceed for flashing this rom starting from an unlocked device with PyxyOs and Askuccio's TWRP?
Thanks in advance.
Andrea.
Click to expand...
Click to collapse
Bluetooth is working fine for me. im using ducasso zest Bluetooth speaker. i didn't know about smart watch connection.
installation is simple. flash stock recovery via twrp or fastboot then flash system.img via fastboot then do factory reset via stock recovery. after that you can use either elemental twrp or askuccio twrp to flash magisk,camera etc.
Ahem. any hope to have a more detailed (step by step) tutorial?
Thanks.
wierd issue
Ramesh006 said:
the development for honor 6x and oreo gsi roms is stopped but only phusson is keep developing oreo gsi rom aosp 8.1 v31. last update was may 3 2019. he did a great job our device. os is complete pure stock,battery backup is amazing and he fixed battery charging speed now device will charge at the speed of stock.
there is two types of firmwares available one is with gapps and root other is without gapps and no root.
first i have tried with gapps version there is no bugs. the only bug is headphones without mic is not detecting. lesser audio switch apk solved that problem.
then i have flased the one without gapps. which is amazing. phone works at its peaks performance, charges faster and drains slower. fingerprint navigation is also improved like if we swipe down it shows notification pannel if we do swipe down again it will expand notification pannel and phone complete navigation can be controlled.
i have flashed cyclox kernel and did over clock for pubg. now pubg runs with smoothes equalls to iphone. i have never got pubg this much smooth, easily wiped out a squad with 7 kills.
without gapps version themed like kitkat and it performance like we are using kitkat on our device.
RAM management is also excellent. it can keep more apps in the memory without killing them.
if we want our device to keep receive google security updates with stable os this is best option.
Download link: https://github.com/phhusson/treble_experimentations/releases/tag/v31
click on assets to get download links.
Click to expand...
Click to collapse
wierd issue, after installing the rom is randomly presing home, im using the one with root and gapps
edit: and now im getting encrypt erros saying im need to wipe but i do that and keep telling me the same
edit2: well i feel kind of stupid XD the random things was a gesture on the print sensor but still dont know why only the gapps and rooted works on my phone, and how did you make the james dsp work mine stop working every time
Link for stock recovery?
Stuck in reboot loop....uff
Ramesh006 said:
Bluetooth is working fine for me. im using ducasso zest Bluetooth speaker. i didn't know about smart watch connection.
installation is simple. flash stock recovery via twrp or fastboot then flash system.img via fastboot then do factory reset via stock recovery. after that you can use either elemental twrp or askuccio twrp to flash magisk,camera etc.
Click to expand...
Click to collapse
I was hoping to get some steps for overclocking the device.
1. Which rom version (gapps/non-gapps) u used?
2. What version of CycloX kernel did u use?
3. What are the settings you're using in the kernel?
Is VoLTE working in them?
mohit.cr.07 said:
Is VoLTE working in them?
Click to expand...
Click to collapse
VoLTE wont work on any lineage or gsi rom
goldenevil47 said:
I was hoping to get some steps for overclocking the device.
1. Which rom version (gapps/non-gapps) u used?
2. What version of CycloX kernel did u use?
3. What are the settings you're using in the kernel?
Click to expand...
Click to collapse
v31 without gapps
kernel version 05. 001 stock 039
just go to 27 page on cyclox kernel and copy the overclock command then give su rights on terminal emulator or termix then paste the commnad and press enter. to check if kernel activated go to root folder honor cfg kernel check overclock is 1. if you reboot your device you need to do it again.