{
"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"
}
Unofficial Cyanogenmod 13 / Android 6.0.1 - Lenovo A850
This is a CM13 rom for our Lenovo A850. This is NOT MY WORK, I found it on this russian forum/post. Unfortunately, i couldn't find further information about the developer since I read the forum through google translate
This is a pure android 6.0.1 and not a looklike rom.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Photos:
Bugs: My problems are...
• I have tried installing Magisk and SuperSu without success (because CM13 is already rooted)
• Lattest Xposed libraried are not working (old may not too)
• Can't always get into recovery using both volume and power buttons (go through the power menu)
• When in the recovery and rebooting into system the phone closes (unplug the batery and reboot it)
• Default (CM) file-manager sometimes craches (for no reason)
• Reboot just powers down the device
• DO NOT INSTALL GRENIFY, you will get into bootloop
• Did you found anything else? Do you know how we can fix the above?
Instructions:
0. MAKE A NANDROID BACKUP! This ROM doesn't do well with you NVRAM... You will probably need to restore your IMEI, your Serial Number would be lost, your Mac Address etc. So... backup.
1. Download the "Lenovo A850 cm13.rar" file from here (there is also a CM12 version, i haven't try it)
2. Google Apps are not installed so you can download them from the Open Gapps Project (ARM->6.0->Any version) or from the above link.
3. Un-rar the "Lenovo A850 cm13.rar" file. The TWRP recovery that is included is translated in Russian (can't change to English) so replace the "recovery.img" file with this View attachment recovery.img that i have cooked (English version).
4. Flash the rom to your phone (there are a lot of videosout there about this)
5. Boot phone and BOOM, CM13/Android 6.0.1!!!!
6. To enable root access or reboot to recovery, open Settings->About->Tap "Build number" many times to unlock Developer Options->go back->Developer Options->Check "Advance reboot" and change "Root access"
7. Keep pressing power button -> reboot -> recovery -> flash Gapps
IMEI Problems/Fixes:
You can fix the IMEI with:
- With MobileUncle (follow these steps)
- Tool Hero (the update of MobileUncle), after that uninstall it.
- Else... if you don't know that you can run IMEI&SN Writer V1.5.3, flash this ROM and try to run it (setup drivers etc). Then FORMAT the phone (with flashtool click format,auto), and flash (click download this time) this ROM(the same with the first link), and then change the IMEI etc with IMEI&SN Writer V1.5.3.
If you liked this topic, click the thanks button <--
did u try this already? is all firmware will work on this? if not, what firmware we need to use in order to flash cm13? thanks
anklesnakim said:
did u try this already? is all firmware will work on this? if not, what firmware we need to use in order to flash cm13? thanks
Click to expand...
Click to collapse
Yes I am already using it, well not daily since its not my main phone. Flashtool is included so it doesn't mater what rom you already have (ROW or CN), you just flash it. I think the ROM is CN though. Additionally, i have tried installing Magisk or SuperSu without a success because CM13 is already rooted. I couldn't change it. What is more, lattest Xposed libraried are not working too (phone freezes and reboots on apk open). Also, i couldn't get into recovery using volume and power button, i am accessing it through the power menu (reboot into recovery). To conclude, when I am in the recovery and I choose to reboot into system the phone closed but I have to unplug the batery and reboot it.
how about battery life?
GreatApo said:
Yes I am already using it, well not daily since its not my main phone. Flashtool is included so it doesn't mater what rom you already have (ROW or CN), you just flash it. I think the ROM is CN though. Additionally, i have tried installing Magisk or SuperSu without a success because CM13 is already rooted. I couldn't change it. What is more, lattest Xposed libraried are not working too (phone freezes and reboots on apk open). Also, i couldn't get into recovery using volume and power button, i am accessing it through the power menu (reboot into recovery). To conclude, when I am in the recovery and I choose to reboot into system the phone closed but I have to unplug the batery and reboot it.
Click to expand...
Click to collapse
I'm also using it (also not my daily device) and overall seems to work no major issues at the moment. I'm happy with the default root and options so I have no conflict with magisk/xposed. I just use the root to remove bloatware and to "tabletize" the phone (freeze sms/telephone/mobile data functions, but can be unfreezed if I need phone functions back again)
I have flashed gapps (pico/customized) version and there is FC if you replace stock clock and messenger with gapps version.
Also battery, this phone without network and screen working (and several apks) disables use to work for some days. Now the battery goes off in 1 day, even if not using. I will try to troubleshoot the culprit.
In lenovo's firmware it had an auto power on-off function that dissapears on this new rom.
Just some further investigation on this rom:
IMEIs are gone, and I am unable to restore them with the typical methods. I will keep on trying
It seems that the battery is drained by "Cell standby" (phone contacting telephony antennas) which is weird, because it has no sim, it's on airplane mode and I have frozen all apks related to phone/mobile data. But looking at the log and at the battery statistics, it's trying to do something with cell data. Also if I go to Phone test and try to "turn radio off", it ignores the click on the button.
I'll try a couple more things but my feeling is that something is wrong on the data system that is linked to the battery drain.
By the way, I have read on the russian forum (source of this post) that cm12 seems to work ok, but I don't want to go to an older version. I'll keep it as a last resource.
sooperior said:
Just some further investigation on this rom:
IMEIs are gone, and I am unable to restore them with the typical methods. I will keep on trying
It seems that the battery is drained by "Cell standby" (phone contacting telephony antennas) which is weird, because it has no sim, it's on airplane mode and I have frozen all apks related to phone/mobile data. But looking at the log and at the battery statistics, it's trying to do something with cell data. Also if I go to Phone test and try to "turn radio off", it ignores the click on the button.
I'll try a couple more things but my feeling is that something is wrong on the data system that is linked to the battery drain.
By the way, I have read on the russian forum (source of this post) that cm12 seems to work ok, but I don't want to go to an older version. I'll keep it as a last resource.
Click to expand...
Click to collapse
I do not have problems with the battery. DO NOT INSTALL GRENIFY, you will get into bootloop. You can fix the IMEI with Tool Hero (the update of MobileUncle). CM12 didn't work for me but there seems to be more users there...
I have tried all the common ways to restore IMEI: Hero, Mtk Droid tools, flashable zips (with/without nvram clear), imei generator and replacing files, changing permissions on /data/nvram, dd from a backup nvram.bin... nothing seems to work. I'm considering reflashing full rom again, just in case something went wrong during flashing.
I have also found a flashable modem firmware, doesn't work either.
Not quite fan of hero though, asks for too many permissions. Don't really get the point of the permissions to read contacts.
Regarding greenify I tried to install but it FC every time. Uninstalled without rebooting, so thanks for the advice. If you have no problem with battery and IMEI, I'm even more convinced that both problems are related.
sooperior said:
I have tried all the common ways to restore IMEI: Hero, Mtk Droid tools, flashable zips (with/without nvram clear), imei generator and replacing files, changing permissions on /data/nvram, dd from a backup nvram.bin... nothing seems to work. I'm considering reflashing full rom again, just in case something went wrong during flashing.
I have also found a flashable modem firmware, doesn't work either.
Not quite fan of hero though, asks for too many permissions. Don't really get the point of the permissions to read contacts.
Regarding greenify I tried to install but it FC every time. Uninstalled without rebooting, so thanks for the advice. If you have no problem with battery and IMEI, I'm even more convinced that both problems are related.
Click to expand...
Click to collapse
I don't like tool hero too, but it did fix my IMEI problem. (I always deny most of the permissions it ask, and then uninstall). Nothing else worked (terminal, recovery, adb).
Battery seems fine here. I have to mention that my charging circuit has major problems. I use the phone daily now and I have 2 batteries charging them with cables.
Well, finally I have decided to re-flash, following the instructions of greatapo at the first post (I'm pretty sure I did the same last time).
In the middle I also flashed lollipop as suggested in the russian forum but I have little confidence that this had any impact.
The point is that phone has "magically" recovered IMEIs (like they were hidden somewhere) and battery usage is back to normal. Before, I had a slope of power comsumption due to cell network even on plane mode. Now, when the phone is idling consumption is flat.
I can recall that this phone (at least my device) had a strange behaviour: When it has been powered off for a while it didn't power on. But if I boot for recovery or keep it on, then it boots perfectly. This time I had it "heating up" before flashing (just in case something similar happens to any of you).
Booting taking too long!
I flashed this ROM with SP Flash Tool (latest). I end up my phone taking too long to boot. I am until now seeing a CynogenMod Marshmallow and some ripple effect behind it
Please. Anybody, tell me the real and proper way to get this ROM working on my Lenovo A850 (step-by-step). Explain Step 4 please.
I am super interested on this ROM!
Maevinarsh said:
I flashed this ROM with SP Flash Tool (latest). I end up my phone taking too long to boot. I am until now seeing a CynogenMod Marshmallow and some ripple effect behind it
Please. Anybody, tell me the real and proper way to get this ROM working on my Lenovo A850 (step-by-step). Explain Step 4 please.
I am super interested on this ROM!
Click to expand...
Click to collapse
Is it everytime or just the first time? First time is absolutely normal, as all aplications have to get compiled
sooperior said:
Is it everytime or just the first time? First time is absolutely normal, as all aplications have to get compiled
Click to expand...
Click to collapse
im in the same situation,stuck on the boot logo for more than half an hour and nothing happened,any help would be great
sooperior said:
Is it everytime or just the first time? First time is absolutely normal, as all aplications have to get compiled
Click to expand...
Click to collapse
Nah Its ok now it works. I am just unable to flash GAPPS. Thats all
Krosbit said:
im in the same situation,stuck on the boot logo for more than half an hour and nothing happened,any help would be great
Click to expand...
Click to collapse
Now is working after flashing the mod above a official rom,now i have 2 errors,i cant see any file when plugged in the pc and the imei one (i tried tool hero but when i apply the apk stopped working),again any help would be great
PS:how can i enable root in the cm12 rom?
sooperior said:
Is it everytime or just the first time? First time is absolutely normal, as all aplications have to get compiled
Click to expand...
Click to collapse
Did you flash ROM+GAPPS successfully? I recently successfully flashed ROM. I tried to flash GAPPS using TWRP but after powering on my Lenovo a850, i always get 2 error message which is (Unfortunately, Setup Wizard has stopped working" (the most) and "Unfortunately, Google play services has stopped working". What now? Did I flashed it wrongly? Can you state how you flash GAPPS please?
Maevinarsh said:
Did you flash ROM+GAPPS successfully? I recently successfully flashed ROM. I tried to flash GAPPS using TWRP but after powering on my Lenovo a850, i always get 2 error message which is (Unfortunately, Setup Wizard has stopped working" (the most) and "Unfortunately, Google play services has stopped working". What now? Did I flashed it wrongly? Can you state how you flash GAPPS please?
Click to expand...
Click to collapse
Yes, my process (the one that finally worked):
Clear (everything but sdcard, modem, etc)
Install android 5 (this might be not necessary)
Clear
Flash cm13
Flash gapps (pico version, the smallest, arm architecture)
Start... and works
I'm starting from a 4.2 CN rom
still invalid imei after using tool hero. please help.
google play store please
gapps on the link page 1 make device force close after flash it via twrp, i do step by step on page 1
and thanks for share
i hope my issue can be solve by anyone here
Maevinarsh said:
I flashed this ROM with SP Flash Tool (latest). I end up my phone taking too long to boot. I am until now seeing a CynogenMod Marshmallow and some ripple effect behind it
Please. Anybody, tell me the real and proper way to get this ROM working on my Lenovo A850 (step-by-step). Explain Step 4 please.
I am super interested on this ROM!
Click to expand...
Click to collapse
same like me
how you solve the problem?
just wait it or do something?
Related
The last thing I remember flashing was Clockword Mod 11 last year, ever since then I have been running Firmware build 18.3.1.C.1.15. Upon seeing an update for my phone for Firmware build 18.3.1.C.1.17 I attemted to download it and kept getting the message "Cannot Verify" so after trying this out on PC Companion and relocking my bootloader I was still running into problems. So the simplest thing I could think of is to use Flashtool and flash the latest ftf from there (Firmware 18.6.A.0.182 - obtained from XperiFirm), at first I didnt think it was a problem to not wipe USER_DATA as I just thought of it as an upgrade, if that failed I persumed I would have to wipe everything (this didnt matter much anyway). So I went ahead and flashed the rom however when I went to boot my mobile I got a bootloop "Android is optimising apps xxx of xxx" this went on forever untill I cut the power using a pin. So I tried it again this time wiping everything and still the same problem :crying: . Then I came across people on the forums to use the older FlashTool verison 0.9.18.6 since the new FSC feature can cause probelms, this time I tried it again however I used the older Firmware 18.6.A.0.172 just to be failsafe. Still the same problem. Right then I was thinking Emma would save my phone so I went and applied the 4.4.4 Firmware 18.3.1.C.1.15 service (Which I had to begin with) but for some reason this seemed to have little effect despite trying it twice and reciving a "Sucessful Flash" message. Now I am left very confused as it is still booting in the lollipop style (optimising apps loop) even though I flashed a KitKat rom. I have been left without my phone all day because of this, any help would be STRONGLY APPRICIATED! . Thanks for your time
#1 Open your bootloader again
#2 Install TWRP (See 5.1.1 root topic for installation/guide)
#3 Open TWRP Wipe all data
#4 Reboot into recovery
#5 Flash any custom rom like Cyanogenmod through TWRP
Post results please this is fixable It's seems It's a soft brick which is an easy fix
What i think is you had corrupt data/left over data and after you relocked bootloader something went wrong after flashing. Though flashing should wipe all data let's see
Re-flash ftf wiping data and caches, you must do this if going from 4.4.4 to 5.1 and From 5.1 to 4.4.4 due to changes in runtime from dalvik to art and other changes.
How to get near enough stock?
Thanks for your replies, when I flashed the ftf's I did tick all the boxes under 'Wipe' on FlashTool, when that failed so did emma. I can try flashing CWM however the main purpose of this was for me to upgrade to Lollipop as I wanted a near enough stock experiance (Considering Z5 Rom) with root. When I tried CWM before there were a few things that I just coulnt get used to. Is there any way that I could use recovery to flash a stock rom with the lastest Lollipop releese or Z5 experiance as I have backups on PCC that I have to restore (Important contacts, media etc...) and I dont really want to use a CWM based rom . I wouldnt mind to flash Z5 however I dont know if this is possiable could you guys comfirm this? Thanks for your time .
[Update] TWRP recovery is working!
I have followed this thread to update my Recovery - TWRP 2.8.7.0 .
Many Thanks to @linuxct for the straight forward instructions and @ARandomIndian for putting me in the correct direction :highfive: .
Im just unsure if I can flash Z5 Experiance Rom now. Is it possiable despite my android being messed? I have already wiped data, is it okay to just go and flash? .
Zane Finch said:
I have followed this thread to update my Recovery - TWRP 2.8.7.0 .
Many Thanks to @linuxct for the straight forward instructions and @ARandomIndian for putting me in the correct direction :highfive: .
Im just unsure if I can flash Z5 Experiance Rom now. Is it possiable despite my android being messed? I have already wiped data, is it okay to just go and flash? .
Click to expand...
Click to collapse
Don't worry you're android is not messed up, let's do this to fix it back to regular :-
Before starting i highly recommend you charge your phone to have atleast 50+% battery and use the official cable provided also make sure the cable is firmly inplace,
#1 Enter Recovery, wipe all data
#2 Download Stock 5.1.1 i think you like that so get that (Make sure it is for your D2303 or whatever your model is)
#3 Install latest flashtools with latest patch (Or later versions if you don't want to risk it)
#4 Go to the location of flashtools (installation directory) for me it is C:\Flashtool\drivers Open the exe file there, select the 2 Flashmode and Fastboot drivers install them.
#5 Flash the ftf using flashtools
Post results
Somehow...
Using TWRP I wiped Dalvik Cache, Cache, System and Data. Using the same 18.6.A.0.182 Customization UK FTF from yesterday I flashed my phone but somehow I am stuck with the same bootloop again?! "Android is optimising Apps XXX of XXX" I really dont understand this. . Thanks for your help .
Zane Finch said:
Using TWRP I wiped Dalvik Cache, Cache, System and Data. Using the same 18.6.A.0.182 Customization UK FTF from yesterday I flashed my phone but somehow I am stuck with the same bootloop again?! "Android is optimising Apps XXX of XXX" I really dont understand this. . Thanks for your help .
Click to expand...
Click to collapse
Hey man Android is optimizing means everything is working just fine it takes about 30+ minutes sometime,
Just leave it charging for atleast 2 hours and see what the progression is and post results please, thank you
Optimising
ARandomIndian said:
Hey man Android is optimizing means everything is working just fine it takes about 30+ minutes sometime,
Just leave it charging for atleast 2 hours and see what the progression is and post results please, thank you
Click to expand...
Click to collapse
Yes but this does not seem normal, the first boot always freezes on the wave animation. It then restarts by itsself and optimises upto so many for example 64 of 200 and then freezes and restarts with a different ammount like 90 of 194. This didnt seem normal to me, is this okay?
Edit: I have left it running for almost 40 min now. Every time just before it seems to freeze and reboot it never reaches the end of the ammount say 60 of 200. I'm becoming very doubtful that it is going to work . But I just remembered a while back that I flashed a custom boot img to get recovery and root in my last working state. Maybe this has somthing to do with it?
Really need my phone working now :| If anyone can help please do! Thanks!
Zane Finch said:
Yes but this does not seem normal, the first boot always freezes on the wave animation. It then restarts by itsself and optimises upto so many for example 64 of 200 and then freezes and restarts with a different ammount like 90 of 194. This didnt seem normal to me, is this okay?
Edit: I have left it running for almost 40 min now. Every time just before it seems to freeze and reboot it never reaches the end of the ammount say 60 of 200. I'm becoming very doubtful that it is going to work . But I just remembered a while back that I flashed a custom boot img to get recovery and root in my last working state. Maybe this has somthing to do with it?
Really need my phone working now :| If anyone can help please do! Thanks!
Click to expand...
Click to collapse
Hi okay, try flashing the Z5 style rom please then we'll move forward I think you've a corrupted ftf
Please redownload latest Z5 style rom make sure it's not interrupted during download. Restart router if needed for stability before download
ARandomIndian said:
Hi okay, try flashing the Z5 style rom please then we'll move forward I think you've a corrupted ftf
Please redownload latest Z5 style rom make sure it's not interrupted during download. Restart router if needed for stability before download
Click to expand...
Click to collapse
I tried flashing the Z5 experiance rom, I followed the instructions on the rom page (Used TWRP). However this time when it booted it did not say "Optimising Android" but it still did boot loop after the wave animation. I also tried flashing the older firmware but that did the same loop again, I also have been looking for alternative ftf's online becuase I also had the suspicion of a corroupted ftf however there are no Customized UK roms availble. I really am stuck now, my phone seems to be more messed up than I thought. . Any more Ideas?
If your bootloader is unlocked did you update it before flashing anything? If not this is why
Zane Finch said:
I tried flashing the Z5 experiance rom, I followed the instructions on the rom page (Used TWRP). However this time when it booted it did not say "Optimising Android" but it still did boot loop after the wave animation. I also tried flashing the older firmware but that did the same loop again, I also have been looking for alternative ftf's online becuase I also had the suspicion of a corroupted ftf however there are no Customized UK roms availble. I really am stuck now, my phone seems to be more messed up than I thought. . Any more Ideas?
Click to expand...
Click to collapse
You updated your bootloader before flashing right? If not do that like Andy said,
Also i would give you my Nandroid but It's the D2305.
[email protected] said:
If your bootloader is unlocked did you update it before flashing anything? If not this is why
Click to expand...
Click to collapse
ARandomIndian said:
You updated your bootloader before flashing right? If not do that like Andy said,
Also i would give you my Nandroid but It's the D2305.
Click to expand...
Click to collapse
Okay, you mean the same one I flashed to be able to update my bootloader to TWRP? I'll give it a shot! Thanks!
Zane Finch said:
Okay, you mean the same one I flashed to be able to update my bootloader to TWRP? I'll give it a shot! Thanks!
Click to expand...
Click to collapse
Okay nice post the results
ARandomIndian said:
Okay nice post the results
Click to expand...
Click to collapse
I flashed that very bootloder before I flashed the Lollipop ftf I booted my phone and the same thing happend, so I tried it again this time flashing afterwards an still booting with the same damn screen . Was I definatly using the correct bootloader or am I missing out anything when flashing? My phones rebooted like 5 times now for the 'optimisation' and its getting nowhere .
Shall I fire up my classic Nokia 5230 with custom Symbian to record a video so you guys can see what happens when it boots?
Did you wipe user data and cache when flashing the ftf
[email protected] said:
Did you wipe user data and cache when flashing the ftf
Click to expand...
Click to collapse
Yes, everything in the 'Wipe' section was ticked, infact before I flashed it again I also wiped Dalvik, cache, data and system in TWRP.
So I just flashed CWM 12.1 and its all running fine for some reason the Wifi doesnt work but atleast I can use this untill we find what the problem is. Do you guys know why my WiFi isnt working? But more importantly why does CWM work and stock rom doesnt?!
Edit: The reason the WiFi isnt working has to be a problem with the kernal as far as I can see, this also suggests that the kernal could be incompatable with Lollipop as it wasnt designed to support it? Correct me if im wrong but if this is the case where can I download the official latest kernal? If someone could confirm this by checking my kernal version above that would be great! Thanks!
I previously updated my kernal here the one that says [new]. If you look at post #8 you will see that this kernal has a problem with WiFi in CWM "As I suspected, in kernel modules there's no WiFi module (wlan.ko), I think that that's the reason why WiFi is not working.
{
"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"
}
Okay flash this version of Cyanogen http://forum.xda-developers.com/xperia-m2/orig-development/rom-cyanogenmod-12-developement-t2971213 choose the latest one
We'll see what the issue can be any ideas @linuxtt
---------- Post added at 03:18 PM ---------- Previous post was at 03:14 PM ----------
Zane Finch said:
So I just flashed CWM 12.1 and its all running fine for some reason the Wifi doesnt work but atleast I can use this untill we find what the problem is. Do you guys know why my WiFi isnt working? But more importantly why does CWM work and stock rom doesnt?!
Edit: The reason the WiFi isnt working has to be a problem with the kernal as far as I can see, this also suggests that the kernal could be incompatable with Lollipop as it wasnt designed to support it? Correct me if im wrong but if this is the case where can I download the official latest kernal? If someone could confirm this by checking my kernal version above that would be great! Thanks!
I previously updated my kernal here the one that says [new]. If you look at post #8 you will see that this kernal has a problem with WiFi in CWM "As I suspected, in kernel modules there's no WiFi module (wlan.ko), I think that that's the reason why WiFi is not working.
Click to expand...
Click to collapse
Okay can you please flash another FTF? First try a new 5.1.1 ftf from another source for your model and then try older versions like Kitkat and post results please
So I decide to upgrade a a couple of weeks after OTA update to CM13 arrived. Turns out it was a massive mistake, especially since no backup, no ADB enabled, no root and nothing custom. This is the best I have so far: https://jira.cyanogenmod.org/browse/BACON-4808 (summary: System UI and com.android.phone both crash on startup). Sad thing is I can see phone working just fine behind the crashed UI (getting mail, notifications etc.) I know my data is in there but cannot get to it.
Anyway, customer support is responsive but I am not sure they will let me keep my data.
I am pretty much starting from scratch regarding flashing, and the first few hours was deciphering abbreviations and other bull. Other than that I am decently proficient with the tech stuff.
Would be grateful if you guys can help point me in the right direction. The info I currently have:
* I want to keep my data
* images here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
* I know that my phone is recognized by PC if I put it into ADB sideload mode (didn't yet try whether it works though)
* phone is also recognized when in fastboot
* possibly downgrade might work, but I am trying to find a method that will let me keep the data, if I get glitches I don't care for now
What I am not so sure about:
* flashing for example cm-12.1-YOG7DAS2K1-bacon-signed.zip in full should let me keep the data, true?
* taking fastboot image and just flashing boot&system should also let me keep the data, true? Did I miss anything?
What do you guys suggest I do? I know that in the end I might crash everything anyway, but at least I want to do the best I can (And make that backup soon after). Thanks for all and any help!
edit: Did the sideload flashing, that went fine, is easy. Problem is those images seem not to work for me anyway (bootloop). Probably because I didn't wipe userdata.
maybe try to use the restore tool (http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851) its pretty old (CM11s) but if it workd then refalsh the TWRP and update your phone to cm12.1 (with the required firmware)
A good question after all I did: Did anyone ever successfully downgrade from 13 to 12.1 without full data wipe?
p.s. it is very very easy to downgrade, it just doesn't work since OS upgrade makes changes to local data making it incompatible. This is what I did:
1) down+power on
2) chose upgrade and sideload upgrade from adb
3) while in that menu phone will wait for the update, just connect it to pc and do adb sideload image.zip (image needs to be signed ordinary image not the fastboot one)
4) wait until it completes and reboot phone
Tried all 4 CM12.1 images to no avail.
Dear all,
After flashing cm-13.0-ZNH0EAS2JK-bacon-signed FROM cm-12.1-YOG7DAS2K1 through TWRP on my rooted OPO as usual i do. MY mobile stuck in boot loader "CYANOGEN MOD READY" And not starting even after 45 mins.
So again i installed cm-12.1-YOG7DAS2K1-bacon-signed. Working fine. Tried many tiimes by wiping data,cache,dalvik too. But every time im stucking at boot loader "CYANOGEN MOD READY" . Please suggest me the best way to shift to marshmallow. I dont want to unroot.
skundurthy said:
Dear all,
After flashing cm-13.0-ZNH0EAS2JK-bacon-signed FROM cm-12.1-YOG7DAS2K1 through TWRP on my rooted OPO as usual i do. MY mobile stuck in boot loader "CYANOGEN MOD READY" And not starting even after 45 mins.
So again i installed cm-12.1-YOG7DAS2K1-bacon-signed. Working fine. Tried many tiimes by wiping data,cache,dalvik too. But every time im stucking at boot loader "CYANOGEN MOD READY" . Please suggest me the best way to shift to marshmallow. I dont want to unroot.
Click to expand...
Click to collapse
Take a backup of your internal storage
Flash factory images of CM13 using Index #8 http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
After flashing factory images, flash TWRP (Index #8)
After flashing TWRP, flash SuperSu from TWRP http://download.chainfire.eu/supersu-stable
I seen Hope for Volte working MIUI8 MM Need Dev. Support
{
"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"
}
xperiaworld said:
I seen Hope for Volte working MIUI8 MM Need Dev. Support
View attachment 4151759
View attachment 4151760View attachment 4151761
Click to expand...
Click to collapse
r u working on this rom ??
how you got the sim cards And Networks showing up in status bar because it was a bug sim cards and network not showing up in status bar but it does show up in settings ??
The project has been probably abandoned so AFAIK no more updates. Even the thread of the ROM is closed.
krishna8691 said:
how you got the sim cards And Networks showing up in status bar because it was a bug sim cards and network not showing up in status bar but it does show up in settings ??
Click to expand...
Click to collapse
Read MIUI rom thread carefully u got the answer...
tywinlannister7 said:
The project has been probably abandoned so AFAIK no more updates. Even the thread of the ROM is closed.
Click to expand...
Click to collapse
Ya but I never give up...It's need soMe R& D .....I m not developer of the rom but I still love to play around it..Hope somebody ready to work on it with me...
can anybody upload it to mirror......i cant find the download anywhere....
rajvansh said:
can anybody upload it to mirror......i cant find the download anywhere....
Click to expand...
Click to collapse
Wait i will post .... Link i found on net....
But i suggest wait for fix..
xperiaworld said:
Wait i will post .... Link i found on net....
But i suggest wait for fix..
Click to expand...
Click to collapse
if u can give link me and my friend can also try to fix bugs.....currently we r working on miui for samsung s5 exynos
xperiaworld said:
Read MIUI rom thread carefully u got the answer...
Click to expand...
Click to collapse
i followed the steps mentioned in the thread but it didnt showed up and i have tried this many times when i installed the rom first time
After restart device quickly double press power button then unlock your phone if locked..It's work for me
Not sure how effective is this method. But worth giving a try partially worked for me.
Based on few posts I came across claiming for working VoLTE.
Note:- Quite a lenthy and time consuming method
Prerequisite :- 1) Stock MARSHMALLOW
2) Stock NOUGAT
3) MIUI
4) TWRPAccording to these posts if you flash MIUI over the Stock nougat(not the soak test) VOLTE should work fine.
Doing so will loose the fingureprint functionality (since it requires stock MARSHMALLOW).
Again doubting on the Volte but I got my fingerprint sensor working(flashed over nougat soak test).
Give a try to this.
[*]1) Backup your Data.
[*]2) Downgrade to Stock MARSHMALLOW.
[*]3) Install TWRP
[*]4) Flash MIUI.
[*]5) Complete Intial setup and configure fingureprint sensor (you will be unable to modify afterwards hence configure as many figures as you want).
[*]6) Go to TWRP backup (MIUI) this rom(Store it on external drive or sd card).
[*]7) Again Downgrade to MARSHMALLOW.
[*]8) Upgrade to Stock Nougat (not the soak test one)
[*]9) Install TWRP
[*]10) Restore (MIUI)
Hopefully this should work. (I didnt tried on Stock Nougat but on Nougat soak test Fingureprint sensor is working properly)
can u share download links......as its been asked several times by sevral user...still no one replies
bravolol said:
can u share download links......as its been asked several times by sevral user...still no one replies
Click to expand...
Click to collapse
rajvansh said:
can anybody upload it to mirror......i cant find the download anywhere....
Click to expand...
Click to collapse
Sorry for late..I have to search lot for it..Bcoz my pc is dead
MIUI8 moto g4 plus https://drive.google.com/file/d/0B78Lx-mWxGVCWDgyZFQwdTJBQmM/view
xperiaworld said:
Sorry for late..I have to search lot for it..Bcoz my pc is dead
MIUI8 moto g4 plus https://drive.google.com/file/d/0B78Lx-mWxGVCWDgyZFQwdTJBQmM/view
Click to expand...
Click to collapse
thanks bro......
:good::good::good::good::good:
SMARTHACKER67 said:
Not sure how effective is this method. But worth giving a try partially worked for me.
Based on few posts I came across claiming for working VoLTE.
Note:- Quite a lenthy and time consuming method
Prerequisite :- 1) Stock MARSHMALLOW
2) Stock NOUGAT
3) MIUI
4) TWRPAccording to these posts if you flash MIUI over the Stock nougat(not the soak test) VOLTE should work fine.
Doing so will loose the fingureprint functionality (since it requires stock MARSHMALLOW).
Again doubting on the Volte but I got my fingerprint sensor working(flashed over nougat soak test).
Give a try to this.
[*]1) Backup your Data.
[*]2) Downgrade to Stock MARSHMALLOW.
[*]3) Install TWRP
[*]4) Flash MIUI.
[*]5) Complete Intial setup and configure fingureprint sensor (you will be unable to modify afterwards hence configure as many figures as you want).
[*]6) Go to TWRP backup (MIUI) this rom(Store it on external drive or sd card).
[*]7) Again Downgrade to MARSHMALLOW.
[*]8) Upgrade to Stock Nougat (not the soak test one)
[*]9) Install TWRP
[*]10) Restore (MIUI)
Hopefully this should work. (I didnt tried on Stock Nougat but on Nougat soak test Fingureprint sensor is working properly)
Click to expand...
Click to collapse
Still volte not works..
xperiaworld said:
Still volte not works..
Click to expand...
Click to collapse
Whats steps you followed.
+
can you validate what this fellow has to say, Due to limited internet i am unable to do so,
https://forum.xda-developers.com/moto-g4-plus/themes/how-to-fix-volte-data-service-hotspot-t3598177
So I need some help and I'm hoping someone here can help.
I've tried, probably 5 or 6 times to flash this rom, but to no avail.
Every time I flash it it says "no sim card"and I know there is an issue with the SIM card error, it's been mentioned many times here. However when I do go into the settings, and I go into "about phone, under "SIM card settings" it shows "no SIM card". During initial set up, I get a pop-up that says 'IMEI cannot be verified." It also says "unknown" for network status (in sim settings). I have no data connection, nor does the phone connect whatsoever (I tried calling a few numbers; no luck).
I've tried flashing just the MIUI rom after a full wipe (including system, dalvik, cache and data) - no luck.
I've tried flashing from both MM and N rom's, doing only a cache and data wipe - no luck there either.
I'd really like to be able to get this rom going on my phone.
Any help or advice is much appreciated. Please, and thank you.
Sent from my Moto G4 Plus using XDA Labs
ricky.smitts said:
So I need some help and I'm hoping someone here can help.
I've tried, probably 5 or 6 times to flash this rom, but to no avail.
Every time I flash it it says "no sim card"and I know there is an issue with the SIM card error, it's been mentioned many times here. However when I do go into the settings, and I go into "about phone, under "SIM card settings" it shows "no SIM card". During initial set up, I get a pop-up that says 'IMEI cannot be verified." It also says "unknown" for network status (in sim settings). I have no data connection, nor does the phone connect whatsoever (I tried calling a few numbers; no luck).
I've tried flashing just the MIUI rom after a full wipe (including system, dalvik, cache and data) - no luck.
I've tried flashing from both MM and N rom's, doing only a cache and data wipe - no luck there either.
I'd really like to be able to get this rom going on my phone.
Any help or advice is much appreciated. Please, and thank you.
Sent from my Moto G4 Plus using XDA Labs
Click to expand...
Click to collapse
You just have to reboot one time when you have this issue and then, you can achieve setup wizzard.
murigny64 said:
You just have to reboot one time when you have this issue and then, you can achieve setup wizzard.
Click to expand...
Click to collapse
I just tried that, still no luck. No phone or data connection. I even tried the "double tap" power button truck; didn't do anything. ?
Sent from my Moto G4 Plus using XDA Labs
tested on ta-1054.
WHY flash ?
nokia system use 2GB memory after boot. there's lots of things auto start. if you try to disable it ,some app else will crash sometime.
in chinese version, there's some spy action in the system apps. for example:
you'll find a folder called "baidu" in /storage/emulated/0/. in the folder,there's some files used to trace your action. but you never installed any app. this is done by a build-in app called weather service.
again, a folder called ".com.nb.filemanager" created by the build-in file manager.
lots of service backend , for example: tencentlocationservice.
in /system/priv-app/cust, there're lots of service only for chinese version. you know what does it mean. and can't be deleted.
treble rom from phh works on my ta-1054. both AOSP and lineageOS works.
it takes only 1.2GB memory when start up. when you install apks, it act fast ,unlike the OEM one ,pause 4seconds more when goes to 90%.
but there's one problem : wifi couldn't be switched on. ------This has been fixed now.
but another problem found. about the calling. when flash the system to slot a, it recognize two sim. both could receive calling.but calling panel will auto quite when calling out. (the other side will ring, but hear nothing when pick up).
when flash the system to slot b, it recognize one sim card only. call and receive ok.
so take your choice, try to go away from rubbish app or not. flash system may brick your phone,take your risk.
HOW TO :
1. unlock your bootloader.
2.backup your things on the phone.
3. fastboot tools. optional: adb tools.
4.download a boot image from https://dospy.wang/forum.php?mod=viewthread&tid=69.
now treble is build on android 8.1, so download B2N-222A-0-00WW-B06-patched-boot.img .
now , i've extracted the stock boot kernal from my nokia 6.1, version android 8.1. use this instead of the former one , the wifi will works.
https://pan.baidu.com/s/1R0ZconptEvAuth5nJt_ekQ
5.download gsi system image :
lineageOS
AOSP [recommend]
important: choose ab one , instead of a only system. choose arm64 instead of arm.
6.turn your phone to download mode.
you may use adb command:
Code:
adb reboot bootloader
or shutdown and hold on volume+ and power key to boot, when a doid picture appear, press these two keys again. then choose reboot to bootloader.
optional: see which slot you are in, a or b:
Code:
fastboot getvar all
check "current sloct:" and remember it. if you faild to start system later, you may go back to fastboot. if you failed to boot ,sometimes the bootloader will load another slot. so, check it. and you could be aware where you are. we flash one slot is enough, two works too.
7. wipe user data,type:
Code:
fastboot -w
8.flash the system image:
Code:
fastboot flash system your-image.img
9.flash the boot image:
Code:
fastboot flash boot B2N-222A-0-00WW-B06-patched-boot.img
tips: if your former system is android 8.1, and you didn't rooted it, then you may skip this step.
10.wipe data again:
Code:
fastboot -w
11.reboot your phone:
Code:
fastboot reboot
ok, you may see lineage os starts up now.
if you want to root your phone, just install magisk.apk, and then add the magisk.zip module. reboot, that's ok.
maybe problem:
fastboot waiting devices.
two reason. 1. your fastboot version . please use the one extracted from android SDK, the one installed by apt install doesn't work. 2. udev rules .add your device ID to /etc/udev/rules.d/51-android.rules.
find your device id by lsusb.
bootloop
if you could enter recovery ,this means boot img ok. try to flash system again. remember to check wich slot you are in. if not the former one, just switch it by "fastboot set_active a/b" a or b choose the currect one.
if you couldn't enter recoery, just flash boot.img again.
This is great an all, but the fundamental issue with all of this is the bootloader unlock. When you say to unlock the bootloader, do you refer to using the paid service to do so?
JBlaze05 said:
This is great an all, but the fundamental issue with all of this is the bootloader unlock. When you say to unlock the bootloader, do you refer to using the paid service to do so?
Click to expand...
Click to collapse
yes, i've paid about 5$ to unlock. I don't know any free way to do it util now. and it's important to do it for me,so i paid.
superium said:
yes, i've paid about 5$ to unlock. I don't know any free way to do it util now. and it's important to do it for me,so i paid.
Click to expand...
Click to collapse
so BL unlocking aside, how smoothly do the GSI's run on this phone compared to the stock rom? Scrolling, fluidity, speed, and whatnot.
JBlaze05 said:
so BL unlocking aside, how smoothly do the GSI's run on this phone compared to the stock rom? Scrolling, fluidity, speed, and whatnot.
Click to expand...
Click to collapse
Good questions!
Good experience :
* it tesk much less time than the stock one when boot.
* It's fast more than the stock one.when start up, it takes about 1.2GB memery, the stock one takes 2GB.
* it's smooth and very pure to use. when installing apps, it's more fast than the stock one. you may notice the stock one will pause several seconds when installing process goes to about 90%.
* there's no so much backround services, like tencentlocationservices, overlay apps for CN ....etc.
* the OTA could recognize all partions when your usb devices have several partitions. the stock one only recognize the first partition.
* the fling navigation is so cool in RRemix and AICP.
Not So Good experience :
* when flash the system to slot a, it recognize two sim. both could receive calling.but calling panel will auto quite when calling out. (the other side will ring, but hear nothing when pick up).
when flash the system to slot b, it recognize one sime only. call and receive ok.
* sms receive will crash the system if you use lineage , RRemix, AICP. Fortunately, the AOSP works good.
* if you use lineageos , scan other blue-tooth devices will crash the system . but transfer files ok.
* if you use lineageos ,AOSP,AICP , you will experience no-response several times. because the Privacy Guard pop toast to ask you allow or deny something, but it freeze the system if it's not the most top app. Fortunately, this will not happen in AOSP because there's no such app.
* when charging in power-off status, can't detect the power percent. (only tested in AOSP)
* compass degree err, all GSI including AOSP.
Additonal
* fly model in the night, about 8 hours. seems lineage and RRemix takes much less power,some version only takes 1%. the AOSP takes about 8%.
* the wifi problem is due to the boot kernal.
now , i've extracted the stock boot kernal from my nokia 6.1, version android 8.1. use this instead of the former one , the wifi will works.
https://pan.baidu.com/s/1R0ZconptEvAuth5nJt_ekQ
superium said:
Good questions!
Good experience :
* it tesk much less time than the stock one when boot.
* It's fast more than the stock one.when start up, it takes about 1.2GB memery, the stock one takes 2GB.
* it's smooth and very pure to use. when installing apps, it's more fast than the stock one. you may notice the stock one will pause several seconds when installing process goes to about 90%.
* there's no so much backround services, like tencentlocationservices, overlay apps for CN ....etc.
* the OTA could recognize all partions when your usb devices have several partitions. the stock one only recognize the first partition.
* the fling navigation is so cool in RRemix and AICP.
Not So Good experience :
* when flash the system to slot a, it recognize two sim. both could receive calling.but calling panel will auto quite when calling out. (the other side will ring, but hear nothing when pick up).
when flash the system to slot b, it recognize one sime only. call and receive ok.
* sms receive will crash the system if you use lineage , RRemix, AICP. Fortunately, the AOSP works good.
* if you use lineageos , scan other blue-tooth devices will crash the system . but transfer files ok.
* if you use lineageos ,AOSP,AICP , you will experience no-response several times. because the Privacy Guard pop toast to ask you allow or deny something, but it freeze the system if it's not the most top app. Fortunately, this will not happen in AOSP because there's no such app.
* when charging in power-off status, can't detect the power percent. (only tested in AOSP)
* compass degree err, all GSI including AOSP.
Additonal
* fly model in the night, about 8 hours. seems lineage and RRemix takes much less power,some version only takes 1%. the AOSP takes about 8%.
* the wifi problem is due to the boot kernal.
now , i've extracted the stock boot kernal from my nokia 6.1, version android 8.1. use this instead of the former one , the wifi will works.
https://pan.baidu.com/s/1R0ZconptEvAuth5nJt_ekQ
Click to expand...
Click to collapse
ok good to hear, i can deal with those cons. ive been wanted to get this phone but i want prices to come down just a bit and i was hoping that the guy who does BL unlocking would publicize his work but oh well. Thanks for the info
I've installed this on the TA-1054 but it says no sim card on both my sim slots. any ideas?
---------- Post added at 03:14 AM ---------- Previous post was at 02:49 AM ----------
I'm getting "No SIM" any ideas?
I have a Nokia ta-1054 with forked firmware so I tried your method. However, I am stuck in powered by Android and I can only enter download mode. I've tried again and again the steps above but I cannot boot normally into android. I've tried different AOSP firmwares, as well as different boot.img, and I cannot enter recovery mode. What can I do?
Metzas said:
I have a Nokia ta-1054 with forked firmware so I tried your method. However, I am stuck in powered by Android and I can only enter download mode. I've tried again and again the steps above but I cannot boot normally into android. I've tried different AOSP firmwares, as well as different boot.img, and I cannot enter recovery mode. What can I do?
Click to expand...
Click to collapse
flash boot file and then fastboot reboot. don't fastboot -w after you flash boot file. this worked for me.
Although the 1054 still cannot recognize my ATT Sim card.
I want to restore my 1054 back to the stock chinese firmware so I can make sure the SIM read error is not a hardware issue but i cannot find the chinese firmware
I also have a TA-1045 USA edition. Is there anyway I can pull the stock image and flash it to my 1054?
Its a paytool for Nokia. Its called ntools they provide and the stock ROMs but is only for these tool
stealthj said:
flash boot file and then fastboot reboot. don't fastboot -w after you flash boot file. this worked for me.
Although the 1054 still cannot recognize my ATT Sim card.
Click to expand...
Click to collapse
Unfortunately that didn't work for me. Is there any other solution or am I stuck with a bricked phone?
Again make sure you are using the correct slots. Then flash, erase userdata, flash boot, fastboot reboot and disconnect USB cable right after pressing enter on fastboot reboot, should reboot into the OS
Anyone try this on TA-1045 yet ?
I have a TA-1050, Does anyone know of the hardware differences between the models and If that would effect the patched boot.img needed? Would it brick if I tried?
TA 1050 supported ?!
this phone is treble enabled by default. not sure why you need to flash a modded boot.img? id flash a rom but there is no way to go back to stock as of now soo ill hold off.
Hi,
Thanks for the guide, however I'm stuck in bootloops no matter which Oreo GSI I'm trying to flash... (Nokia TA-1043, went straight from stock > unlocked bootloader > 8.1 AOSP > stuck on bootanimation)
Solannae said:
Hi,
Thanks for the guide, however I'm stuck in bootloops no matter which Oreo GSI I'm trying to flash... (Nokia TA-1043, went straight from stock > unlocked bootloader > 8.1 AOSP > stuck on bootanimation)
Click to expand...
Click to collapse
Same on TA-1043
Managed to flash back stock firmware using Ntool. My phone's working fine now
After installing TWRP (all version for 1043) phone will stuck either at bootlogo or opens TRWP, but never runs OS.
I don't know how often I reflashed System and Boot, at the moment I flash TWRP, it stops workung. Any ideas?
After some flashing of TWRP it showed a "decrypted message" and internal SD was full of unrecognizable trash-files.
{
"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"
}
Evolution X 5.2 for the OnePlus 7 Pro [guacamole]
Code:
/*
* Your warranty is void. Or vaild, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modificiations, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/
Living, Breaking, Keep Evolving.
Pixel UI, customization and more, we are Evolution X!
- Team Evolution X -
@joeyhuab
@peaktogoo (Now RealAkito)
Reach us on Twitter! @EvolutionXROM
What are our features?
- Just flash and check "The Evolver"
single tap gesture doesn't work, WFD doesn't work and No Verizon Network Support
DO NOT FLASH GAPPS, ALREADY INCLUDED
DO NOT FLASH GAPPS, ALREADY INCLUDED
First Time Install / Clean Flash
1. Have latest OOS 10.x flashed to both slots!!
2. Download the proper flashable ZIP for your device
3. Reboot to Recovery
4. Wipe Data/Cache/System
5. Format Data (Required)
6. Flash the ROM
7. Reboot to System
8. Reboot to Recovery (Optional)
9. Flash Magisk (Optional)
10. Reboot to System and #KeepEvolving
Update / Dirty Flash
1. Reboot to Recovery
2. Download the proper flashable ZIP for your device
3. Reboot to Recovery (Optional)
4. Flash Magisk (Optional)
5. Flash the ROM
6. Reboot to System and #KeepEvolving
Light Screenshots / Dark Screenshots / Download
Donate to me! / Official Chat / Device Support
Android OS version: 11.0_r20
Security patch level: December 2020
Build Author: Justin Crawford
Source Code: https://github.com/Evolution-X
Kernel Source Code: https://github.com/Justasic/kernel_oneplus_sm8150
ROM Developer: joeyhuab
Thanks: npv12, spookcity138, chandu dyavanapelli, madgeniusgamer
Reserved
Screenshots by Android 10 ????
I have Evolution X android 10. And it's amazing it has so many features and modification Love it. Does EvoX 11 have all of these features and even more? keep up the good job
Wait, this has OOS cam AND is Android 11? SICK! Does normal Magisk Beta work or do we need that modded Magisk that's been floating around?
@justasic What version of the camera program?
Just a heads up, not sure if my phone is just weird, but the first wipe instructions (step 4), resulted in my device only being able to boot to bootloader and resulting in " FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" if i try to flash or do anything on CMD/fastboot now. Not sure if it's bricked or if this will happen to you, and it's obviously not a ROM issue, but just mentioning it just incase anyone is following the exact steps.
Nice ROM,so smooth,,dualboot with MSM xtended rom,
Video with OOS Cam crash,,even with shortcut,,
Parkourkid93 said:
Just a heads up, not sure if my phone is just weird, but the first wipe instructions (step 4), resulted in my device only being able to boot to bootloader and resulting in " FAILED (remote: 'Failed to load/authenticate boot image: Load Error')" if i try to flash or do anything on CMD/fastboot now. Not sure if it's bricked or if this will happen to you, and it's obviously not a ROM issue, but just mentioning it just incase anyone is following the exact steps.
Click to expand...
Click to collapse
Dont wipe system,,just do format data
muphetz said:
Dont wipe system,,just do format data
Click to expand...
Click to collapse
Too late, I already learned the hard way bro. I'm pretty sure it was bricked since I couldn't even get into recovery, just kept booting back to the bootloader. I unbricked it and i'm & running now though. Great rom so far, I noticed the initial UI lag that seems to be common on every A11 roms I tried for the oneplus 7, but it goes away once you refresh the screen, so no big deal. A major issue for me though is that Google FI doesn't seem to activate. When I try to it just tells me "Unfortunately your Google FI service can't be activated because your account currently isn't authorized for service". Which sounds like it's an issue with my account, but when I log into fi via my desktop, nothing seems out of the ordinary, I even randomly used the sim on a t-mobile sim locked iPhone, downloaded FI and it activated without an issue. I'm gonna go back to stock & see if it happens there. Will report back in a few.
To everyone else, don't let this discourage you from trying this rom out. Like i mentioned before, great rom so far & I appreciate the upload, I loved Evolution on Pixel 3. Just need my service lol
Parkourkid93 said:
Too late, I already learned the hard way bro. I'm pretty sure it was bricked since I couldn't even get into recovery, just kept booting back to the bootloader. I unbricked it and i'm & running now though. Great rom so far, I noticed the initial UI lag that seems to be common on every A11 roms I tried for the oneplus 7, but it goes away once you refresh the screen, so no big deal. A major issue for me though is that Google FI doesn't seem to activate. When I try to it just tells me "Unfortunately your Google FI service can't be activated because your account currently isn't authorized for service". Which sounds like it's an issue with my account, but when I log into fi via my desktop, nothing seems out of the ordinary, I even randomly used the sim on a t-mobile sim locked iPhone, downloaded FI and it activated without an issue. I'm gonna go back to stock & see if it happens there. Will report back in a few.
To everyone else, don't let this discourage you from trying this rom out. Like i mentioned before, great rom so far & I appreciate the upload, I loved Evolution on Pixel 3. Just need my service lol
Click to expand...
Click to collapse
MSMTool will save your life on this, also I recommend not using Step 4. Skip to Step 5. Wiping will erase OOS off the phone.
SaintZ93 said:
MSMTool will save your life on this, also I recommend not using Step 4. Skip to Step 5. Wiping will erase OOS off the phone.
Click to expand...
Click to collapse
Unless I straight up downloaded the wrong MSMTool, the one posted here on our forums didn't seem to work for me, said something about a firmware mismatch or something and I couldn't seem to find the correct fastboot rom for my current firmware. I've never used it before though so it's highly possible I did something wrong. What worked for me was extracting the files from the latest stock OOS, dumping all the files from the payload.bin using python, then just manually flashed whichever files it pulled from the .bin.
I'm currently back on stock OOS now though & Google FI works again without any issues. I'll deff try this again on the next update.
Parkourkid93 said:
Unless I straight up downloaded the wrong MSMTool, the one posted here on our forums didn't seem to work for me, said something about a firmware mismatch or something and I couldn't seem to find the correct fastboot rom for my current firmware. I've never used it before though so it's highly possible I did something wrong. What worked for me was extracting the files from the latest stock OOS, dumping all the files from the payload.bin using python, then just manually flashed whichever files it pulled from the .bin.
I'm currently back on stock OOS now though & Google FI works again without any issues. I'll deff try this again on the next update.
Click to expand...
Click to collapse
My question would be, what type of OP7P do you have. The one from OnePlus or the one from T-Mobile? If TMO then there is a different MSMTool you will need to use.
SaintZ93 said:
My question would be, what type of OP7P do you have. The one from OnePlus or the one from T-Mobile? If TMO then there is a different MSMTool you will need to use.
Click to expand...
Click to collapse
Good question, I bought it off of Amazon like a year ago though, so I don't have a 100% answer on that. Since I've gotten the device, I was able to OEM unlock, flash twrp, magisk etc. off the rip. I even dual simmed it with Google FI & Mint together without any issues and I use the global stock .zip from the OnePlus site everytime I update. If there's a way to check for sure, deff lemme know & I'll get back at you. Message me though since this isn't really ROM related & I don't want to clutter up the thread.
Set up works fine, getting an unusal issue where the framerate is locked at 30fps, anyone else having this issue?
*Edit* Typical, I reboot to install magisk, and now it is working fine. Nevermind me!
H4X0R46 said:
Wait, this has OOS cam AND is Android 11? SICK! Does normal Magisk Beta work or do we need that modded Magisk that's been floating around?
Click to expand...
Click to collapse
You can use magisk v21.2 or the modded one, it seems the fastboot issues were fixed in v21.2.
Eagle-no1 said:
@justasic What version of the camera program?
Click to expand...
Click to collapse
OOScam version 3.8.114, I didn't focus a lot on getting camera working quite yet which is why it still has some crashes, should be getting fixed as best I can in the next few updates.
ImjustSaiyan92 said:
Set up works fine, getting an unusal issue where the framerate is locked at 30fps, anyone else having this issue?
*Edit* Typical, I reboot to install magisk, and now it is working fine. Nevermind me!
Click to expand...
Click to collapse
This framerate issue is because I am forcing 90hz from the kernel (since automatic 90hz needs some work still), just lock the device and unlock it and it will go away.
Parkourkid93 said:
Unless I straight up downloaded the wrong MSMTool, the one posted here on our forums didn't seem to work for me, said something about a firmware mismatch or something and I couldn't seem to find the correct fastboot rom for my current firmware. I've never used it before though so it's highly possible I did something wrong. What worked for me was extracting the files from the latest stock OOS, dumping all the files from the payload.bin using python, then just manually flashed whichever files it pulled from the .bin.
I'm currently back on stock OOS now though & Google FI works again without any issues. I'll deff try this again on the next update.
Click to expand...
Click to collapse
hmm I only had to use msmtool once in my experience, generally as long as you're able to get to fastboot and you've already oem unlocked, you can go back to oos usually by fastboot booting a recovery image and flashing from there. I have not heard of Google FI before so I will look into this, we just merged our January security patch so I'll be making a new release soon and it might be related to that. I've not had any issues with wiping system on my device and I keep it there in case others are looking to come from other roms. Wiping vendor would cause issues though which is why I have flashing oos there but you're welcome to skip the wiping system step as I don't believe it will cause problems since the rom flashes over system anyway.
Done all the steps. Cant connect to my home wifi, I enter password and nothing happens. Any ideas? Wifi worked before on android 11