Hello everybody...
This post was created with the intention of helping those people who want to upgrade their baseband version of ZUK Z2+. There are some methods to do this, some of them could erase all your information (qfil) and some others could block bootloader (.zip).
The presented method in this post will not erase either your data or block your bootloader.
Note: when I say "data" I'm referring to images, downloads, videos, etc. This method won't erase any data located on root/sdcard.
Here are the steps for upgrading baseband:
1: Download this ROM and transfer it to you cellphone. (NOTE: It's highly recommended to download it from your PC. I downloaded it through my phone and at the time of flahing, it gave me an error; It said it was a corrupt file. So, download it through your PC.)
2: Go to TWRP and wipe system, data, cache and dalvik cache.
3: Flash the ROM and be patient.
As the aim of this post is upgrading the baseband, some of you might wonder "Is it necessary to boot up so that baseband could be updated?", I don't actually know it. When I installed this ROM at first I wasn't after a baseband upgrade, rather taste it to see how it was (btw, it's the best nougat ROM so far; my humble opinion). So, we could say that you can try not to wait till it boot up, and install your whished ROM right after the first flashed ROM. But I highly recommend you to taste this ROM.
IMPORTANT DATA: this ROM will update baseband to 1.70 version.
There is a more recent version than the one used on the steps above (I do not know whether this version is capable of upgrading baseband or not. I tried to root that version with Magisk 15.3 but unable to). Here is the ROM.
If you decided to taste this ROM you should know that the only available languages are Chinese and English, and flashing gapps' zip won't work. In order for you all to solve gapps problem do the following:
1: Download Google Installer 2.0
2: Install, open and download all fundamental data from Google Installer
3: For contacs app to work properly do the fallowing: go to settings/apps/Google Contact Sync/Permissions, grant all permissions and restart your phone.
This ROM includes some chinese apps, but those can be disabled very easily if you go to apps' window.
LongTap does not work on this ROM.
Thanks to @Not_James_Bond for providing me the GoogleDrive's link of the ROM, since the official website is weibo and it's a little bit tedious download things from there.
Reserved :v
How to enable swipe up open dockon this ROM like Oreo some days ago I did but now i cant find that option but when I installed other ROM I forgot how to do that
can u please help me ??
dawoodrangrez said:
How to enable swipe up open dockon this ROM like Oreo some days ago I did but now i cant find that option but when I installed other ROM I forgot how to do that
can u please help me ??
Click to expand...
Click to collapse
You just have to update OnePlus Launcher...
MaikelAt said:
Reserved :v
Click to expand...
Click to collapse
Please make a video showing the features, home screens, VoLte, camera etc and post it on youtube that will be greatly appreciated.
Thanks
rakeshsainixyz said:
Please make a video showing the features, home screens, VoLte, camera etc and post it on youtube that will be greatly appreciated.
Thanks
Click to expand...
Click to collapse
On YouTube there are some reviews... Like this one or others
Is there a similar rom for indian variant which updates baseband to 1.76???
MaikelAt said:
Here are the steps for upgrading baseband:
1: Download this ROM and transfer it to you cellphone. (NOTE: It's highly recommended to download it from your PC. I downloaded it through my phone and at the time of flahing, it gave me an error; It said it was a corrupt file. So, download it through your PC.)
2: Go to TWRP and wipe system, data, cache and dalvik cache.
3: Flash the ROM and be patient.
...
IMPORTANT DATA: this ROM will update baseband to 1.70 version.
...
Click to expand...
Click to collapse
OMG...
Do you seriously think that to change the baseband you need to flash a new ROM ???
It is necessary to follow closely the answers to your questions. Everything is much simpler.
https://forum.xda-developers.com/showpost.php?p=75337122&postcount=881
Nordicus said:
OMG...
Do you seriously think that to change the baseband you need to flash a new ROM ???
It is necessary to follow closely the answers to your questions. Everything is much simpler.
https://forum.xda-developers.com/showpost.php?p=75337122&postcount=881
Click to expand...
Click to collapse
Maybe you got him all wrong. It's the safest way bcz on Zukfans thread some zips lock bootloader so we have to flash unlock img right after baseband flashing. If anyone boots without flashing img he/she may lose his internal storage . So it's imp to flash unlock img before booting up the device right after updating baseband.
abhi8192 said:
Is there a similar rom for indian variant which updates baseband to 1.76???
Click to expand...
Click to collapse
I don't actually know... I'll try to find it out and let you know...
Related
12/06/2014: I created a Greek generic pre-rooted 12.1.A.1.205 made with @quetzalcoatl2435 guide.
Download.
07/04/2014: 12.1.A.1.201 made with @quetzalcoatl2435 guide. Includes be2_album for Bravia Engine fix.
Download.
Mirror but with zipped file (needs unzipping to get the flashable zip).
To root --> Follow this guide.
To CWM --> Follow this guide.
To flash Rom:
-------------
1. Boot in CWM.
2. Clear dalvik cache, wipe cache, wipe data.
3. Flash the Rom zip.
4. Flash SuperSU 1.93.
5. POWER OFF <-- Very important or you will get bootloop!.
6. (Old:Flash .201 kernel with flashtool in flashmode). Flash .205 kernel with flashtool in flashmode from a .205 ftf firmware file choosing first to exlude everything but kernel. Or you can flash .205 kernel sin file with flashtool in fastboot mode, guide.
subwrc said:
I created a Greek generic pre-rooted 12.1.A.1.201 made with @quetzalcoatl2435 guide.
Download.
To root --> Follow this guide.
To CWM --> Follow this guide.
To flash Rom:
-------------
1. Boot in CWM.
2. Clear dalvik cache, wipe cache, wipe data.
3. Flash the Rom zip.
4. Flash SuperSU 1.93.
5. Power off.
6. Flash .201 kernel with flashtool in flashmode.
Click to expand...
Click to collapse
Is the kernel same for all country's and Models ?
Rushaan™ said:
Is the kernel same for all country's and Models ?
Click to expand...
Click to collapse
According to this post i think so, but I can' t tell you for sure.
Thanks
subwrc said:
According to this post i think so, but I can' t tell you for sure.
Click to expand...
Click to collapse
Thanks for answering my question
Have a nice day
If it's a flash able zip, then why does your title says FtF
Sent from my C5303 using Tapatalk
neXus PRIME said:
If it's a flash able zip, then why does your title says FtF
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
Oh sorry! I corrected it!
subwrc said:
I created a Greek generic pre-rooted 12.1.A.1.201 made with @quetzalcoatl2435 guide. Includes be2_album for Bravia Engine fix.
Download.
To root --> Follow this guide.
To CWM --> Follow this guide.
To flash Rom:
-------------
1. Boot in CWM.
2. Clear dalvik cache, wipe cache, wipe data.
3. Flash the Rom zip.
4. Flash SuperSU 1.93.
5. Power off.
6. Flash .201 kernel with flashtool in flashmode.
Click to expand...
Click to collapse
Thanks for this ,but for newbies the how to is a bit scant
for example -
Where is the Rom. zip as per -
3. Flash the Rom zip.
and is this all i have to do, as in will i then have Greek 12.1.A.201 on my phone after this -
6. Flash .201 kernel with flashtool in flashmode.
also, as this is a Greek rom, will i be able to read the menus as i am not Greek?
...please pardon all the noob questions, just wanna be sure so i dont brick my phone
b00b said:
Thanks for this ,but for newbies the how to is a bit scant
for example -
Where is the Rom. zip as per -
3. Flash the Rom zip.
and is this all i have to do, as in will i then have Greek 12.1.A.201 on my phone after this -
6. Flash .201 kernel with flashtool in flashmode.
also, as this is a Greek rom, will i be able to read the menus as i am not Greek?
...please pardon all the noob questions, just wanna be sure so i dont brick my phone
Click to expand...
Click to collapse
In (3) i mean to flash the downloaded rom from the link i gave, witch is a zip file.
Yes you can change language and read the menus.
Here is a detailed guide but for another rom file.
subwrc said:
In (3) i mean to flash the downloaded rom from the link i gave, witch is a zip file.
Yes you can change language and read the menus.
Here is a detailed guide but for another rom file.
Click to expand...
Click to collapse
Most appreciated subwrc
Please delete it.. wrong section..
Is this for C5302 or C5303?
Also, do you have to "wipe data" or can you keep your data so when you start the phone after completing the installation, all your apps still remain?
Xadious said:
Is this for C5302 or C5303?
Also, do you have to "wipe data" or can you keep your data so when you start the phone after completing the installation, all your apps still remain?
Click to expand...
Click to collapse
It's for C5303.
I think you can keep your data partition but haven't tried though. Do a backup first.
I am running 121A1201 official.What should i do to install this rom .I ask this because as i see this guide is referred to people who have not already updated to 201...
Thanks in advance!
Theorw said:
I am running 121A1201 official.What should i do to install this rom .I ask this because as i see this guide is referred to people who have not already updated to 201...
Thanks in advance!
Click to expand...
Click to collapse
You have to do everything from the beginning as described in the first post. Root, install recovery and flash rom.
Thank you for the kernel itself. My C5303 (Central Europe) now works flawlessly with ROOT. DooMLoRD kernel had problems with RAM.
I bit the bullet and done this upgrade (from android v4.12 to now android v4.3) and it went well
So now i have android 4.3 on my xperia sp and i also have my data intact too as i chose not to 'wipe data' before flashing, however i did clear dalvik cache and wipe cache.
Most important though, is that i can now use three (3 uk) 4g (LTE), which i couldnt use without upgrading to android v4.3
For the curious this is what I used (and i followed the instruction here -http://forum.xda-developers.com/showpost.php?p=51654818&postcount=1) -
- pre-rooted.C5303_12.1.A.1.201_Generic GR_1272-4887.zip - (the rom in this thread using the link provided by the OP in the 1st post in this thread)
- UPDATE-SuperSU-v1.93.zip - (using the link provided by the OP in the 1st post in this thread)
- recoverys_signed_040414_162006.zip --- (my new recovery - for more see here - http://forum.xda-developers.com/showpost.php?p=50359355&postcount=1)
Now that i am happy with the upgrade, my question to those who have upgraded to android v4.3 is this -
(1). for security i used to use LBE Security Guard in v4.12 and it worked okay, however the version i have does not seem to be working properly on android v4.3, especially the blocking of apps from using the internet (4g/LTE) ...any known solutions with regards to this app?
(2). Likewise for security i used to use Xprivacy on android 4.12 but however it too does not seem to be working properly all the time now and i suspect that its because i still have installed the version i had before upgrading to v4.3, any suggestions as to the version of Xprivacy that anyone on v4.3 are now using please?
correction
just realised no wifi after upgrade
wifi does turn on but no router shows up and i am surrounded with routers and even if i manually add a router or access point, it does not do anything when i click on the newly created access point.
Anyone having this issue and any suggestion pls?
b00b said:
correction
just realised no wifi after upgrade
wifi does turn on but no router shows up and i am surrounded with routers and even if i manually add a router or access point, it does not do anything when i click on the newly created access point.
Anyone having this issue and any suggestion pls?
Click to expand...
Click to collapse
You may have to try a clean install.
subwrc said:
You may have to try a clean install.
Click to expand...
Click to collapse
Actually the problem has been traced back to the ROM, something to do with symlink, see here for fix after upgrade -
http://forum.xda-developers.com/showthread.php?p=52662520
Thanks to the OP in that post, his post and subsequent solution saved me a lot of headache and maybe me posting this here will help others in a similar situation
Updated to .205.
This is considered a beta rom. Things may break, things may change, and your phone may brick or turn into a portable toaster. I'm not responsible.
You are flashing this at your own risk!!!
This is a nandroid backed up from a US 2gb/16gb xt1540. It may or may not work on all models...that is to be determined.
Confirmed compatible variants:
XT1540 (US 1/8GB and 2/16GB) (Canada)
XT1541 (UK) (France)
(if your variant is not here it only means it's either not tested or not reported working. please test and report back!)
If you are unable to boot or obtain any signals after flashing this, it is highly recommended you flash a full factory image intended for your specific model and wait for another solution.
This is only meant to be a temporary fix while we wait for the big guys to build us a standard rom.
PLEASE READ THE GUIDE BELOW!!! Some things have changed with v3
How to install:
Extract the .tar.gz archive like any zip
copy the folder to the directory where your other TWRP nandroids are on your internal storage or sd card (TWRP/BACKUPS/ZZY222____/) in here you will see folders with dates, times, rom names and info, etc in the folder names...copy the folder you extracted to this directory.
boot to TWRP
restore this backup
if coming from anything but a previous soak test, wipe userdata
wipe cache and dalvik cache
flash systemless root zip SuperSU v2.61 (optional) DO NOT flash any lower SuperSU version!!
reboot (Please be patient...it's a VERY long wait. If you pass 10 minutes waiting and it hasn't booted, force a reboot by holding the power button)
profit!
***It is HIGHLY recommended US xt1540 users update their radio. It is not required to run this soak test, though. THIS IS ONLY FOR US USERS!!!!! DO NOT FLASH THIS IF YOU ARE NOT IN THE UNITED STATES!!!!***
See this post for the updated soak test modem.img files (just flash to the modem partition with fastboot and reboot the device)
http://forum.xda-developers.com/201...-devs-moto-g3-xt1540-soak-test-files-t3255643
For anyone who is not in the contiguous USA (48 states) but still has xt1540 and would like to test the modem above, you can use the app linked below to back up your modem partition directly from your device before you try the new modem. This way you don't have to download a factory rom to get the right modem.img if you don't already have one backed up on your computer. You have to be rooted to use it.
Wanam Backup & Restore app (free)
How to root:
Please see this thread for the download:
http://www.xda-developers.com/update-to-snapprefs-xposed-module-includes-17-instagram-like-filters
The newest root method provided by chainfire does not touch the system partition. To the end-user, the only change is that when you flash a new kernel you must re-flash superSU....not your rom!!! What this means to us in this case is we can use the stock kernel provided with the soak test, flash the superSU zip, and have root, just like a Nexus device without having to wait for a permissive kernel!
*****After flashing the new systemless root zip you will be prompted to install superSU before the device reboots. DO NOT ALLOW IT TO INSTALL!!!!!! If you allow it to install with this option you will get a bootloop*****
**To view your device storage from your computer, open your notification shade, click the "USB for _____" notification, and select "transfer files (MTP)". It won't stick through a reboot, so you'll have to do this each time you boot.....the same thing goes if you unplug the cable.
Download:
https://drive.google.com/file/d/0ByE999IDa0JnaEpnX0FCRjNxX28
Gonna try it on my xt1540. Just one question about the procedure. I just restore backup directly? Without wiping anything? Or should i wipe system at least?
feligoni said:
Gonna try it on my xt1540. Just one question about the procedure. I just restore backup directly? Without wiping anything? Or should i wipe system at least?
Click to expand...
Click to collapse
TWRP wipes for you automatically in the restore process. You don't have to wipe system manually. Just restore wipe userdata and reboot!
hp420 said:
TWRP wipes for you automatically in the restore process. You don't have to wipe manually. Just restore and reboot!
Click to expand...
Click to collapse
Awsome. Im downloading the file right now, gonna report back when i try it
feligoni said:
Awsome. Im downloading the file right now, gonna report back when i try it
Click to expand...
Click to collapse
I'm reuploading a new nandroid...please wait to install the new version
hp420 said:
I'm reuploading a new nandroid...please wait to install the new version
Click to expand...
Click to collapse
Haha, ok. I was about to restore te backup, but i'll wait.
I'm very sorry for any inconvenience guys. I know it was a very large download. This next one is about half the size.
hp420 said:
I'm very sorry for any inconvenience guys. I know it was a very large download. This next one is about half the size.
Click to expand...
Click to collapse
Dont worry, i've got pretty good download speed at work hehe
All done! new link in the OP guys...go nuts
610mb??
Sarath280 said:
610mb??
Click to expand...
Click to collapse
it's system and boot only, and compressed.
it's all there, trust me
hp420 said:
All done! new link in the OP guys...go nuts
Click to expand...
Click to collapse
Things look good, right now it's in the eternal process of optimizing apps Just wondering, by upgrading like this, i will get updates via ota? or only if u keep updating it?
feligoni said:
Things look good, right now it's in the eternal process of optimizing apps Just wondering, by upgrading like this, i will get updates via ota? or only if u keep updating it?
Click to expand...
Click to collapse
We will only get an update if our friend who is an official tester shares it with us.
Okay, it worked. I booted up perfectly, but as i needed my phone completely stable for today i reverted back to LP. But it worked well I think ill wait for a stable version though, it kind of lagged compared to LP.
feligoni said:
Okay, it worked. I booted up perfectly, but as i needed my phone completely stable for today i reverted back to LP. But it worked well I think ill wait for a stable version though, it kind of lagged compared to LP.
Click to expand...
Click to collapse
Glad it worked!! Thanks for reporting back
it booted on xt1550 ril not working
Sarath280 said:
it booted on xt1550 ril not working
Click to expand...
Click to collapse
have you tried manually entering your carrier's APN information?
I'm having issues extracting the System folder from the backup.
Any ideas? Trying to cook up a flashable ROM for easier testing.
l3ones said:
I'm having issues extracting the System folder from the backup.
Any ideas? Trying to cook up a flashable ROM for easier testing.
Click to expand...
Click to collapse
you can extract with any of the popular file managers for android right on your phone if you'd like. It may take a little longer, but it will work.
hp420 said:
you can extract with any of the popular file managers for android right on your phone if you'd like. It may take a little longer, but it will work.
Click to expand...
Click to collapse
Apparently it was just an issue with 7-zip, WinRAR handled it perfectly.
This is my first time making a flashable ROM but it should be up later today.
After installing MedroM I got this problem and couldn't connect to google account and every google app would crash if I tried to log in, so I flashed b161 and I still have this problem, even after numerous factory resets, has this ever happened to anyone ?
Yes, it is happening to other guys around here...
In fact is happening to all who flash B160/B161 firmware...
Is not possible to flash any firmware previously to B160/B161.
Workaround is to unlock bootloader, flash twrp, root it, reflash oeminfo for your device,
and after that you can flash another firmware again.
gtdaniel said:
Yes, it is happening to other guys around here...
In fact is happening to all who flash B160/B161 firmware...
Is not possible to flash any firmware previously to B160/B161.
Workaround is to unlock bootloader, flash twrp, root it, reflash oeminfo for your device,
and after that you can flash another firmware again.
Click to expand...
Click to collapse
i'm in the same situation, i tried to do what you've said, but twrp says that the installation failed. how can I have play store working again? please help, this situation is driving me crazy!
i'm on c900 b161.
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
After 2 days of trying different stuff, here's what gave me a functional device with TWRP and Root back:
-Back up any data you want to keep, obviously.
-Reflash stock ROM (put UPDATE.APP on your dload/ folder on the separate SD card, then boot into the update function by turning the phone off and then holding Vol+, Vol-, Power. Just wait until it's finished.
-Unlock Bootloader again
-Download the Toolkit: http://forum.xda-developers.com/huawei-p9lite/development/europe-vns-l31-toolkit-bootloader-t3432873
-Flash TWRP through the toolkit
-Boot TWRP and root
-In Android, enable ADB
-In the Toolkit, go to Dual Sim>Individual and select the appropriate custom.bin and oeminfo.img from the thread of the toolkit. For my European one it was L31 SS C432. Press flash and grant Root permissions on your phone.
-Turn off your phone and flash the stock ROM again like in step 1.
-If you want root, you need to unlock the Bootloader again, flash TWRP and then root it from there.
DON'T WIPE ANYTHING IN TWRP OR YOU WILL HAVE TO START ALL OVER AGAIN!
Don't ask me how I know.
Hope this saves someone from wasting their time with this nonsense like I have.
No need to touch the oem stuff, just extract the boot.img and system.img and flash through adb, for dat you need bootloader unlocked and fastboot drivers then you can downgrade firmware and fix your sign problem or just wait for a new firmware
raffabraz said:
No need to touch the oem stuff, just extract the boot.img and system.img and flash through adb, for dat you need bootloader unlocked and fastboot drivers then you can downgrade firmware and fix your sign problem or just wait for a new firmware
Click to expand...
Click to collapse
That would be much simpler, I didn't consider that. Would you mind writing up a guide?
I've had the same issue and have resolved it pretty easily,
i did the following steps ;
- download both medrom versions
- do full factory reset
- install medrom v1
- do all settings of google etc
- reboot recovery and install v2
- wipe dalvik and reboot
-- all works now except for the forceclose on facebook
ps : this answer is also in the thread ( not as extended as this but it's there )
Edit : some other apps are Force closing to, my guess is that there's a shared resource of some kind that's corrupted or something..
sirlex said:
I've had the same issue and have resolved it pretty easily,
i did the following steps ;
- download both medrom versions
- do full factory reset
- install medrom v1
- do all settings of google etc
- reboot recovery and install v2
- wipe dalvik and reboot
-- all works now except for the forceclose on facebook
ps : this answer is also in the thread ( not as extended as this but it's there )
Edit : some other apps are Force closing to, my guess is that there's a shared resource of some kind that's corrupted or something..
Click to expand...
Click to collapse
Force closing is caused by the oeminfo in my experience. Can you check in the "About Phone" section which build number your phone currently has? Should be something along the lines of "VNS-L31C432B161" where C432 indicates the region code.
since I am Running MEDROM v2 it shows just that. However , I do know it is based on b161
HeavyHDx said:
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
After 2 days of trying different stuff, here's what gave me a functional device with TWRP and Root back:
-Back up any data you want to keep, obviously.
-Reflash stock ROM (put UPDATE.APP on your dload/ folder on the separate SD card, then boot into the update function by turning the phone off and then holding Vol+, Vol-, Power. Just wait until it's finished.
-Unlock Bootloader again
-Download the Toolkit: http://forum.xda-developers.com/huawei-p9lite/development/europe-vns-l31-toolkit-bootloader-t3432873
-Flash TWRP through the toolkit
-Boot TWRP and root
-In Android, enable ADB
-In the Toolkit, go to Dual Sim>Individual and select the appropriate custom.bin and oeminfo.img from the thread of the toolkit. For my European one it was L31 SS C432. Press flash and grant Root permissions on your phone.
-Turn off your phone and flash the stock ROM again like in step 1.
-If you want root, you need to unlock the Bootloader again, flash TWRP and then root it from there.
DON'T WIPE ANYTHING IN TWRP OR YOU WILL HAVE TO START ALL OVER AGAIN!
Don't ask me how I know.
Hope this saves someone from wasting their time with this nonsense like I have.
Click to expand...
Click to collapse
Thank you so much , you saved my phone !!
Fllashing stock rom again isnt necessary , just flash the oeminfo, reboot, they will tell you an encryption password, so you have to do a factory reset AND DONE !
simo255 said:
Thank you so much , you saved my phone !!
it doesn't need to reflash stock rom again, just flash the oeminfo, reboot, they will tell you an encryption password, so you have to do a factory reset AND DONE !
Click to expand...
Click to collapse
Interesting, when I tried to do a factory reset after that screen, it always failed.
HeavyHDx said:
Interesting, when I tried to do a factory reset after that screen, it always failed.
Click to expand...
Click to collapse
You have to flash the stock recovery to do a Factory reset
medRom v2 fix
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Could someone provide me the correct oeminfo and custom.bin for a European/German model? C432? The images inlcuded in the toolkit don't work for me, it still crashes or can't communicate with the google server
Deddline said:
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Click to expand...
Click to collapse
Installing Android System Web View apk from apkmirror solved the problem for me (arm + x86 package). Thank you
HeavyHDx said:
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
Click to expand...
Click to collapse
I got my P9 Lite from Congstar in Germany. I didn't knew, that the device would be branded by Telekom. I flashed the B161 and couldn't connect to any google account. Thankfully updating the webview apk via apk mirror solved this problem. But this leaves me with 2 questions and maybe you could answer these...?
1) Do you know which stock rom would work the best with my device (VNS-L31 without the possibility to use two sim cards ) and where I could download this stock rom.
2) Is the B161 supposed to work fine after solving this issue or are there other problems with it?
I would be really happy if someone of you could help me. :good:
MartinMo said:
1) Do you know which stock rom would work the best with my device (VNS-L31 without the possibility to use two sim cards ) and where I could download this stock rom.
2) Is the B161 supposed to work fine after solving this issue or are there other problems with it?
Click to expand...
Click to collapse
1) The best stock ROM would either be, well, the stock ROM, or the Revolution ROM.
2) I've had some strange behavior with Relay for Reddit and frequent crashes of WhatsApp when sending messages. Right now I'm on Lineage OS 14.1 and it's really great. Camera's a bit slow, but otherwise I love it. I missed stock Android.
HeavyHDx said:
1) The best stock ROM would either be, well, the stock ROM, or the Revolution ROM.
Click to expand...
Click to collapse
Isn't Nougat still a beta...? I'm looking for a stable stock version of EMUI...
HeavyHDx said:
2) I've had some strange behavior with Relay for Reddit and frequent crashes of WhatsApp when sending messages. Right now I'm on Lineage OS 14.1 and it's really great. Camera's a bit slow, but otherwise I love it. I missed stock Android.
Click to expand...
Click to collapse
Thank you, tomorrow I'll test if Whatsapp working fine or not, that's important for me. Is Lineage 14.1 the most stable Lineage version?
Nougat is still in beta, yes. The full version is expected to come out within the next few weeks.
14.1 refers to the Android version which is 7.1.1. They adopted CyanogenMod's naming scheme. You'll still need to update LineageOS to get bugfixes and such. The dev releases a new update every 2 or 3 days, just check their website periodically.
Deddline said:
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Click to expand...
Click to collapse
Installed Android System Web Viev .apk did the trick for me, too. muchos gracias.
I'm already try flash trough TWRP over leaked official nougat version.
Works fine just dalvik and cache wipe after flash.
this is international ver. (not like hydrogen Eng/Chinese only)
original post from official forum
https://forums.oneplus.net/threads/oxygenos-open-beta-1-n-for-oneplus-3t.482846/
If i were to flash over my stock OS, what do I need to delete (without losing pictures etc). I keep forgetting..
I have read that TWRP has some errors when flashing, not sure what this was.
vincedyne said:
If i were to flash over my stock OS, what do I need to delete (without losing pictures etc). I keep forgetting..
I have read that TWRP has some errors when flashing, not sure what this was.
Click to expand...
Click to collapse
Hi
You can try side-load, but you need backup for sure.
my device is root and bootloader is open and I have already Nougat beta ver. before there so my upgrade was quick and all files and settings remains.
hampik said:
Hi
You can try side-load, but you need backup for sure.
my device is root and bootloader is open and I have already Nougat beta ver. before there so my upgrade was quick and all files and settings remains.
Click to expand...
Click to collapse
Ahh. I'll look into this, thanks!
hampik said:
Hi
You can try side-load, but you need backup for sure.
my device is root and bootloader is open and I have already Nougat beta ver. before there so my upgrade was quick and all files and settings remains.
Click to expand...
Click to collapse
So you just flashed the zip in TWRP and SuperSU afterwards? Or did it take additional steps?
bmwbasti said:
So you just flashed the zip in TWRP and SuperSU aftwerwards? Or did it take additional steps?
Click to expand...
Click to collapse
No additional steps. Flash the zip, supersu and wipe cache and everything is working fine.
I'll give it a shot eventhough i'm still on 3.5.4 and not the leaked beta.
I'm guessing as this will have the original boot.img (kernel), as no custom Nougat kernels are yet built (have to wait on the source code) that it will once flashed Encrypt the phone again? Thus the need for the pin/password for twrp?
No point in flashing Open Beta; th official stable OTA is coming tonight too.
https://twitter.com/getpeid/status/815171834345885696
Deleted
So seems there are soon to be two channels beta and stable coming. Great stuff!
Are the sources for ROM and kernel up yet?
Can we side load this over the top of the leaked nougat ROM ?
Moderator Information,
Thread closed, we do not need multiple threads for this.
From the forum I followed these step to install magisk:
- Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot
- After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally
- After booting up installed Magisk Manager and both Magisk and Magisk manager shows green tick (installed)
But at this stage, whenever I open Magisk, it shows a recommendation to install a ZIP, if I agree to install it, phone gets stuck in recovery again.
If I choose not to install recommended zip and click Install > Direct Install, phone gets stuck in recovery again anyway
Everytime it gets stuck I have to wipe all data and start all over again. Anyone else facing same issue? Any solution?
Really frustrated right now.
My current rom is : DAVINCIIN INDIAN Global_V11.0.2.0
Used latest magisk manager 7.4.0
I have official recovery, not TWRP.
Afraid that flashing TWRP now will brick it for good.
UPDATE: Got the solution here, thanks @pikchu289 !
Twrp up to now is the best way
But check some stuff first
1.unlock the boot loader
2.chech if the magisk zip/img is corrupted or any file
3.does your os support this magisk version
Any way you can flash twrp because many people had already tried it and tested it from installing zips/ROMs/mods etc.. to backup files/data or even fixing some corrupted files that caused boot loops manually
But there are various things that doesn't work usually such as restoring system partition but never worry about this because if any thing failed just use miflash tool to go back to official/stock rom
Edit : I think something's wrong with your magisk version number
I have no idea which rom youre using or why on earth you didn't install TWRP before messing around with the os but some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch
Solve this solution
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
pikchu289 said:
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
Finally someone with an answer!
Thanks... Will try and see if it works...
UPDATE: IT WORKED!
Aserar said:
I have no idea which rom youre using
Click to expand...
Click to collapse
Maybe I should've used font size 72 while writing the rom I'm using above.
Aserar said:
why on earth you didn't install TWRP before messing around with the os
Click to expand...
Click to collapse
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
Aserar said:
some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch
Click to expand...
Click to collapse
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-
It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
stone_henge said:
Maybe I should've used font size 72 while writing the rom I'm using above.
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-
Click to expand...
Click to collapse
Aserar said:
It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
Click to expand...
Click to collapse
Sorry for being harsh... I understand you actually tried to help. It's actually really frustrating when facing a problem that has no straightforward solution.
Sorry mate.
finally i founded how to fix this issue without formating data of ur device
--just the flash the same the full custom rom or stock rom that u r using currently on . and boom restart. and ur issue fixed
Install a magisk zip without TWRP. TWRP takes too long. Instead use Aodin to flash a rom specific to your device version. Make sure it is not corrupted as well