Related
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.
Hi
I got my self in quite a pickle here..
so advice or help is very welcomed.
I own a Huawei P10 lite,
with a software version WAS-LX1AC900B049
First off I unlocked the phone, then flashed TWRP recovery, and thus far everything was ok
I wanted to install Lineage 14.1 OS, and I failed because my version of the phone is not supported..
but during attempt installation of Lineage OS , I deleted data, system, dalvik, and cashe..
I did not make a backup!!! (major mistake, I know..)
so effectively I deleted my OS :-/ ..
but it isn’t over jet..
because I could not find a stock rom, namely WAS-LX1AC900B049 version
I thought of debranding my phone to Orange, namely WAS-LX1AC109B110 because stock roms for Orange are available on the net.
so.. using TWRP I replaced oeminfo file..
(this time making a backup of oeminfo)
but once I downloaded Orange stock rom, put it on the
sdcard in /dload folder and entered download mode on the phone, nothing happened, update failed
but.. also changing oeminfo resets the system so I guess that turned off USB debugging..
so now the TWRP is not available because of the system reset, and in the fastboot and rescue mode , adb program from Windows, does not detect device..
so..
it seems I have 3 options..
1. somehow install Orange stock rom
2. make fastboot and rescue mode to work properly so I can reinstall TWRP and go further from there
3. find original stock rom WAS-LX1AC900B049, may be it will work
by the way erecovery does not work, it conects to the wifi, starts serching, and then fails
Help please..
I unbricked the phone
for anyone interested I used adb to unlock the phone in fastboot and rescue mode..
the phone was showing me a message that it was unlocked but it was not
once unlocked previously installed TWRP booted immediately, so from there I installed Lineage 14.1 by HassanMirza01 and it works great
Happy that you fixed your problem but how did adb detected your device as you mentioned it didn't at the first place?
Planning on going back to stock and I think the same trouble would happen for me too.
oH MY GOD!
ultragorki said:
Hi
I got my self in quite a pickle here..
so advice or help is very welcomed.
I own a Huawei P10 lite,
with a software version WAS-LX1AC900B049
First off I unlocked the phone, then flashed TWRP recovery, and thus far everything was ok
I wanted to install Lineage 14.1 OS, and I failed because my version of the phone is not supported..
but during attempt installation of Lineage OS , I deleted data, system, dalvik, and cashe..
I did not make a backup!!! (major mistake, I know..)
so effectively I deleted my OS :-/ ..
but it isn’t over jet..
because I could not find a stock rom, namely WAS-LX1AC900B049 version
I thought of debranding my phone to Orange, namely WAS-LX1AC109B110 because stock roms for Orange are available on the net.
so.. using TWRP I replaced oeminfo file..
(this time making a backup of oeminfo)
but once I downloaded Orange stock rom, put it on the
sdcard in /dload folder and entered download mode on the phone, nothing happened, update failed
but.. also changing oeminfo resets the system so I guess that turned off USB debugging..
so now the TWRP is not available because of the system reset, and in the fastboot and rescue mode , adb program from Windows, does not detect device..
so..
it seems I have 3 options..
1. somehow install Orange stock rom
2. make fastboot and rescue mode to work properly so I can reinstall TWRP and go further from there
3. find original stock rom WAS-LX1AC900B049, may be it will work
by the way erecovery does not work, it conects to the wifi, starts serching, and then fails
Help please..
Click to expand...
Click to collapse
YOU DID AS EXACTELLY AS ME ...HAHAHAHAHAHAHAH and now im still tryiong to find it solutution ...have you found some?
I recently bought a LeEco Le S3 X522 Qualcomm Snapdragon 652 chip set from aliexpress.com Phone already came WITH EUI 5.8.021S Build IFXNAOP5802141S installed With google apps. No OTA update, and
SIM Slot 1 supports full range of services, including voice call, data services and VoLTE/Wi-Fi calls. While SIM Slot 2 supports GSM voice calls and SMS only.
The only difference between Le 2 and S3 is the version of Quick charge and the ROM, every other thing remains the same.
I know to solve the problem of only one slot using voice call, data services and VoLTE/Wi-Fi calls is simply changing the ROM, which I did and it worked. But I don't like the fact that on the back of the phone, the model is written as Le X522 and the in about phone it is X520, so I decided to update the phone.
So I downloaded a stock ROM from https://devsjournal.com/download-letv-official-stock-rom.html#Le_S3_X522_8211_US_Le_2_Pro_Stock_ROM to download EUI 5.9.028
1523502484_FULL_S2_PLUS_S2_PLUS-CN-FN-HEXCNFN5902812161S.zip tried to install it and i got error message saying "Updater process ended with ERROR: 7 Error installing zip file 1523502484_FULL_S2_PLUS_S2_PLUS-CN-FN-HEXCNFN5902812161S".
Okay, I deleted the 2 lines from updated-script saved it and tried it again and still got the same error.
I downloaded another file. 1523442203_S2_X520-CN-FN-IEXCNFN5902802011S-5.9.028S.zip with the same error 7 but after editing the script it installed but got stock after patching system image i will upload screenshots so I really don't know what to do and where to get a working ROM EUI 5.9.026 or EUI 5.9.028
Thanks in Advance
I think you flashed the wrong rom.That rom is for "le_x6" MTK devices (X620/X626).
Download X522 rom and reflash.
Version 28s has problem with google services, better to flash older versions.
Search for it in the forums here or on needrom.
Bobfish said:
I think you flashed the wrong rom.That rom is for "le_x6" MTK devices (X620/X626).
Download X522 rom and reflash.
Version 28s has problem with google services, better to flash older versions.
Search for it in the forums here or on needrom.
Click to expand...
Click to collapse
Thanks for your reply.
I have that in mind also, but the first ROM I installed is Le S3 (X522 – US Le 2) Pro Stock ROM and the second Le 2 (Qualcomm) Stock ROM hung at the end so had yo force reboot phone. The screenshot is there
Is the bootloader unlocked?If bootloader is already unlocked , and Twrp installed, it won't boot stock rom.You need to root with Magisk.
Download Magisk zip and install from Twrp.
Don't do this if bootloader is locked, you'll brick the phone.
Bobfish said:
Is the bootloader unlocked?If bootloader is already unlocked , and Twrp installed, it won't boot stock rom.You need to root with Magisk.
Download Magisk zip and install from Twrp.
Don't do this if bootloader is locked, you'll brick the phone.
Click to expand...
Click to collapse
Thanks, the bootloader is unlocked, if the bootloader is locked I don't think I would be able to install TWRP. I noticed any ROM with S2 will work and ROM with X6 don't work is it that S2 is for snapdragon and X6 is for MTK?
Again I got another phone (same phone) installed TWRP and Backed up the ROM and tried to restore it into the other phone and it didn't load the backup (it didn't see the file just the folder) what do I really need to do to get the restore working or get the latest snapdragon rom for S3?
Yes , X6 is Mtk chipset.
Maybe try wipe cache/data/dalvik, then root with Magisk zip.
If that doesn't work, download and flash X522 Eui 5.8 just to get the phone to boot up.
Just saw this:
https://forum.xda-developers.com/le-2/how-to/sd-652-firmware-stock-rom-5-9-023s-t3632277
I'd mistakenly downloaded and flashed "T520UEUAOD1_T520XARAOD1_HOME.tar.md5" which is Chinese and no Google apps or anything, then I tried falshing "T520UEUAOD1_T520XARAOD1_HOME.tar" which is US I assume, but I fail at system.img everytime on Odin, is there a way I can flash it? Because without it, I can't even install LineageOS into this Tab as system framework force closing at boot along Google services Any help is appreciated
Copy paste error? Md5 is a hashing algorithm, which can be used to verify the integrity of another file. I think you have the US file.
Make sure you have factory reset, and that you are not installing gapps over a stock ROM.
After flashing back oxygen os to both slots I can't download all my apps. Putting the phone to download google backup(like apps and such) it fails to install over 40 apps out of 170 and when trying to update apps, playstore says that the app which I'm trying to update needs SD card or other media device with sufficent space while i have over 90gb free. I have also tried to use the unbricking tool with no luck. WhatsApp doesn't want to restore either. I've also tried to download ota file with chrome and chrome says also that I don't have enough space.
Try fastboot
You should try flash again with fastboot-ROM
Thevili03 said:
After flashing back oxygen os to both slots I can't download all my apps. Putting the phone to download google backup(like apps and such) it fails to install over 40 apps out of 170 and when trying to update apps, playstore says that the app which I'm trying to update needs SD card or other media device with sufficent space while i have over 90gb free. I have also tried to use the unbricking tool with no luck. WhatsApp doesn't want to restore either. I've also tried to download ota file with chrome and chrome says also that I don't have enough space.
Click to expand...
Click to collapse
Use msm tool instead...i got this issue when came back from custom rom! Some partition is messing up
Thevili03 said:
After flashing back oxygen os to both slots I can't download all my apps. Putting the phone to download google backup(like apps and such) it fails to install over 40 apps out of 170 and when trying to update apps, playstore says that the app which I'm trying to update needs SD card or other media device with sufficent space while i have over 90gb free. I have also tried to use the unbricking tool with no luck. WhatsApp doesn't want to restore either. I've also tried to download ota file with chrome and chrome says also that I don't have enough space.
Click to expand...
Click to collapse
I had the same problem after make a oos reinstall with a .bat I download, I solved the problem copying all the internal memory to my pc and making a full wipe (internal memory included) and a reinstall via fastboot with the .bat
maybe copy and wipe the internal memory and reinstall the rom can solve the problem, if not I can upload the fastboot unbrick .bat I use to gdrive and you can try a reinstall it is oos pie 9.0.17 but you can always update to oos 10
So, I got it to working with msm-tool. It went back to oos 9.0.16 and then I upgraded to oos 10.3.5, resetted again, and got everything working. But now I think that I got the Indian version or something, because I have red cable club and oneplus cloud there, I live in Finland so obviously they aren't working here. Can I somehow get the international version of oos?
For anybody reading this in the future, this is actually caused by invalid decryption keys. It's possible to have Android boot but not successfully decrypt data. In this state the phone will boot but no applications will install and saving files won't work correctly.
Simply wiping data should fix the issue, but there's always the MSM tool for when things go really wrong.
use fastboot roms to refresh your device and remove data encryptions
Thevili03 said:
So, I got it to working with msm-tool. It went back to oos 9.0.16 and then I upgraded to oos 10.3.5, resetted again, and got everything working. But now I think that I got the Indian version or something, because I have red cable club and oneplus cloud there, I live in Finland so obviously they aren't working here. Can I somehow get the international version of oos?
Click to expand...
Click to collapse
International/global same thing. There are twrp flashable OOS that are global for 6t here: https://forum.xda-developers.com/oneplus-6t/how-to/oneplus-6t-global-repo-oxygen-os-builds-t3865396
Next time you want to roll back to OOS from a custom rom:
Boot twrp
Flash OOS 10.3.5 global from that link
Flash twrp installer zip
Flash finalize zip
Format data (remember this wipes everything)
Reboot system.
You will not have this issue if you install that way.
Then if you want root boot twrp and flash magisk , reboot system.
Also if you ever have to use Msm tool again you can use the last Android 9/pie twrp by mauronofrio. The twrp he compiled just before Android 10/Q twrp started.. You can use that twrp and just flash OOS 10.3.5 global rom after you run Msm tool. That way updating won't take so long. That's what I did and had no issues. Just don't ever downgrade OOS via TWRP or you'll brick.