Hello. I have d855 android 5.0 . Wanted to install cm 13. and here are my steps:
1. Rooted my 5.0 , flashed TWRP, and flashed CM13 and gapps. There was a problems with dialer after flash, so i downgraded phone into 4.4.2 V10a (using .tot and .dll files) . .
2. Again tried to flash CM13, but process was aborted and phone bricked.
3. Flashed stock 4.4.2 again. Again no luck to write CM .
4. Flashed stock 5.0 v21a using lg flashtool. Again - if i want to flash CM - phone always bricked (error executing updater binary) . And now, even with stock 5.0 my phone data connection do not work (only wifi works)
Please help .... how to reflash my phone and get CM and back data connection??
Just tried flash 4.4.2 again. Flashed successfully, but still any data connection Tried update into 5.0 using phone software updater, but after few updaters it fails (invalid software package).
Today found, that data connection works perfectly if i set GSM/WCDMA . If LTE is selected, there are no data connection at all. Also, can't flash custom rom, phone always stuck at LG logo. Anybody can help so solve my problems?
imdarex said:
Hello. I have d855 android 5.0 . Wanted to install cm 13. and here are my steps:
1. Rooted my 5.0 , flashed TWRP, and flashed CM13 and gapps. There was a problems with dialer after flash, so i downgraded phone into 4.4.2 V10a (using .tot and .dll files) . .
Click to expand...
Click to collapse
I want to cite only the first point you described, because it's "abominable"!
Sorry for the harsh tones, but... the dialer issues obviously involved the Cyanogen rom, especially because you're using the first nightlies, often unstable.
Why you accused the official firmware (therefore no more existing since you replaced them) and decided to downgrade?
Then you've to known that important downgrades like Lollilop > KitKat may irreversibly corrupt system partitions like "efs", which make your device losing of IMEI code and mobile data!
Now the only thing you can do is updating your device by settings menu until you reach latest firmware (21A).
Since you've to manually confirm each updates (10A, 10E, 20A etc.), the process will take almost 1-2 hour.
When the update process in definitely completed, you can try to root device, install TWRP and flash latest CM13 nightly.
In case of other issues, try the quite stable CM 12.1, or the stock-based FulmicsRom.
If you continue to have troubles, do a CSE flash of 21A firmware and send your device to warranty.
Simone98RC said:
I want to cite only the first point you described, because it's "abominable"!
Sorry for the harsh tones, but... the dialer issues obviously involved the Cyanogen rom, especially because you're using the first nightlies, often unstable.
Why you accused the official firmware (therefore no more existing since you replaced them) and decided to downgrade?
Then you've to known that important downgrades like Lollilop > KitKat may irreversibly corrupt system partitions like "efs", which make your device losing of IMEI code and mobile data!
Now the only thing you can do is updating your device by settings menu until you reach latest firmware (21A).
Since you've to manually confirm each updates (10A, 10E, 20A etc.), the process will take almost 1-2 hour.
When the update process in definitely completed, you can try to root device, install TWRP and flash latest CM13 nightly.
In case of other issues, try the quite stable CM 12.1, or the stock-based FulmicsRom.
If you continue to have troubles, do a CSE flash of 21A firmware and send your device to warranty.
Click to expand...
Click to collapse
Last time I connected my phone to LG mobile support, and it automaticallly updated my phone into newest official 21A firmware. IMEI - OK, data connection - still do not work when LTE is selected. So what i need to do now ? Try to root, install TWRP and flash CM 12.1 or FulmicsRom ?
imdarex said:
Last time I connected my phone to LG mobile support, and it automaticallly updated my phone into newest official 21A firmware. IMEI - OK, data connection - still do not work when LTE is selected. So what i need to do now ? Try to root, install TWRP and flash CM 12.1 or FulmicsRom ?
Click to expand...
Click to collapse
So what's your problem when LTE is enabled?
Mobile data won't work or simply fallback to HDSPA?
Simone98RC said:
So what's your problem when LTE is enabled?
Mobile data won't work or simply fallback to HDSPA?
Click to expand...
Click to collapse
When LTE is enabled, then there are no data connection at all.
imdarex said:
When LTE is enabled, then there are no data connection at all.
Click to expand...
Click to collapse
Surely downgrading the entire firmware to the first release of KitKat broke the radio part of your device.
Probably if you downgraded to latest KitKat firmware (10h maybe, instead of 10a), LTE should works properly.
Have you encountered that connectivity issue even before flashing CM 13 (on official firmware)?
Simone98RC said:
Surely downgrading the entire firmware to the first release of KitKat broke the radio part of your device.
Probably if you downgraded to latest KitKat firmware (10h maybe, instead of 10a), LTE should works properly.
Have you encountered that connectivity issue even before flashing CM 13 (on official firmware)?
Click to expand...
Click to collapse
No, after flashing everything was fine. There is a way to reflash radio part without downgrading again ? Because when i spoted that data connection do not working, i downgraded firstly to 10a (no data connection), then i get 10h update - still no data connection. And after 10h update, my phone got another update, but showed that can't update because package is wrong of something. After that i flashed 21A what i have in my phone now.
imdarex said:
No, after flashing everything was fine. There is a way to reflash radio part without downgrading again ? Because when i spoted that data connection do not working, i downgraded firstly to 10a (no data connection), then i get 10h update - still no data connection. And after 10h update, my phone got another update, but showed that can't update because package is wrong of something. After that i flashed 21A what i have in my phone now.
Click to expand...
Click to collapse
Probably the mobile data issue was related to CM 13.
But when you downgraded to 10A, the radio part was really damaged.
As I said if you want to downgrade, always preger the "less old" firmware you need.
Like you, I downgraded in past to KitKat, but I never looked for 10A! I directly flashed 10H.
Sorry, but at this point I don't know what you have to do.
When you flashed 21A firmware, have you done a CSE flash instead of a normal one?
If not, do it.
If yes, you have to appeal to warranty without any problem, since your device has official firmware.
Simone98RC said:
Probably the mobile data issue was related to CM 13.
But when you downgraded to 10A, the radio part was really damaged.
As I said if you want to downgrade, always preger the "less old" firmware you need.
Like you, I downgraded in past to KitKat, but I never looked for 10A! I directly flashed 10H.
Sorry, but at this point I don't know what you have to do.
When you flashed 21A firmware, have you done a CSE flash instead of a normal one?
If not, do it.
If yes, you have to appeal to warranty without any problem, since your device has official firmware.
Click to expand...
Click to collapse
Yes, i did CSE flash. Ok, thank you. I think there are no more options than warranty.
I didn't root HTC's android 7.0 but unlocked it from htcdev's site, was able to push on TWRP 3.0.2.0 and can boot into it, backed up HTC's ROM and tried flashing on several ROMs but in each case the cellular radio is inactive (can't even do a #*#*4636*#*# -- dialer numbers are grey) even after letting the phone sit for an hour, rebooting a few times.
I restore HTC's ROM and the cell radio is all good. If I wipe DATA and setup the M9 from scratch, the cell radio is still good.
Any ideas?
If the roms aren't based on nougat you'll have problems. The rom MUST match the firmware.
Beamed in by telepathy.
shivadow said:
If the roms aren't based on nougat you'll have problems. The rom MUST match the firmware.
Click to expand...
Click to collapse
They all were/are based on nougat.
Zenfone 2 Deluxe Special Edition
Model: Z00A
Before I unlocked, rooted, and flashed my current version, I had Android M - I believe it was Asus firmware version: WW-4.21.40.352
Current version: Groovy Android Android N (7.1.2) - GA-N-v7.1.2-20180612-Z00A-Release.zip
Apparently that was a big mistake and I should have downgraded to Android L before flashing Groovy Android Android N because there's a known issue related to the SIMs not being detected.
I can get my LTE connection to work if I physically remove and reinsert the SIM but that's obviously annoying. And I figured out how to play with the data/SIM settings to get it to register on the data network again but it keeps reverting back to having issues with the X over the LTE symbol and having no data connection.
I just picked Groovy Android because I didn't really know where to start and I wanted Android Nougat. I really want a dark themed Android Nougat but I haven't come across any custom ROMs that have that option. Any suggestions?
For now, I need to go back to Android L so I can flash Groovy Android again without SIM issues.
I downloaded UL-Z00A-WW-2.20.40.206-user.zip from Asus's website.
Can I simply go into TWRP, go into sideload mode, and then type adb sideload UL-Z00A-WW-2.20.40.206-user.zip from my PC?
Do I need to wipe any particular partitions before or after?
EDIT:
Oh also one of the reasons I wanted to try a custom ROM is because of all the bluetooth audio issues I was having. Every single ROM I've ever had on this phone, from the one it shipped with, through several OTA and updated firmwares from Asus's website that claim to "fix bluetooth stability", I've always had this issue where the audio just randomly cuts out while connected to my Soundbot SB360 receiver (I've had other devices and phones connected to it without issue). I've seen other people complain about it on Asus's forums with no real resolution.
That does not happen on my device. It's stable except for the crashed pie
I know I need to downgrade to stock Lollipop. So the question is, can I do that from TWRP, and how do I do it?
Did you back up your system partition before flashing Groovy Android?
If not: https://forum.xda-developers.com/zenfone2/help/guide-flash-stock-rom-asus-zenfone-2-t3588276
nastys said:
Did you back up your system partition before flashing Groovy Android?[/url]
Click to expand...
Click to collapse
Yeah, but how does that help me get to Lollipop?
I was on Marshmallow prior to Groovy Android.
download asus flash tool
download raw rom
flash it on stock recovery
flash rom lolipop stock zip
accomplished
Everything you can download and find on the forum
orificium said:
Yeah, but how does that help me get to Lollipop?
I was on Marshmallow prior to Groovy Android.
Click to expand...
Click to collapse
Either flash the firmware directlyhttps://forum.xda-developers.com/zenfone2/help/guide-flash-stock-rom-asus-zenfone-2-t3588276, or restore that backup, flash stock MM recovery, lock the bootloader and downgrade by installing the 2.x "update" zip from ASUS's website.
nastys said:
Either flash the firmware directlyhttps://forum.xda-developers.com/zenfone2/help/guide-flash-stock-rom-asus-zenfone-2-t3588276, or restore that backup, flash stock MM recovery, lock the bootloader and downgrade by installing the 2.x "update" zip from ASUS's website.
Click to expand...
Click to collapse
I was reading over this guide yesterday and I'm going to try METHOD 2 using the Asus Flash Tool to flash WW_ZE551ML_2.20.40.206_20170627.raw which is the latest version of Lollipop.
Hello,
I have been on BPA1 for a long time for a number of reasons, mainly I was afraid to upgrade and lose the ability to unlock the bootloader if I eventually wanted to do that. I disabled the OTA update notification and service a long time ago. But I am ready to upgrade now because I want WiFi calling on 6.0.1 and many apps are stopping support for 5.1.1.
I have looked around at these forums and I think I understand how to upgrade to 6.0.1, but I would appreciate an idiot check.
Current status:
Fully stock 5.1.1 N910VVRU2BPA1 Firmware
Goal:
Fully stock 6.0.1 N910VVRU2CQL1
Proposed steps:
Download and extract ODIN: ODIN3-v3.13.3.zip
OTA Update from N910VVRU2BPA1 to N910VVRU2CPD1: https://www.androidfilehost.com/?fid=24572369360126104
Flash N910VVRU2CQL1: (have not found this file yet)
I have a couple of questions about this:
Will this wipe the data on my phone (e.g. installed apps, settings, etc.)?
If so, is there any way to get to CQL1 without having to wipe my phone?
Am I missing anything?
ScheissSchiesser said:
Hello,
I have been on BPA1 for a long time for a number of reasons, mainly I was afraid to upgrade and lose the ability to unlock the bootloader if I eventually wanted to do that. I disabled the OTA update notification and service a long time ago. But I am ready to upgrade now because I want WiFi calling on 6.0.1 and many apps are stopping support for 5.1.1.
I have looked around at these forums and I think I understand how to upgrade to 6.0.1, but I would appreciate an idiot check.
Current status:
Fully stock 5.1.1 N910VVRU2BPA1 Firmware
Goal:
Fully stock 6.0.1 N910VVRU2CQL1
Proposed steps:
Download and extract ODIN: ODIN3-v3.13.3.zip
OTA Update from N910VVRU2BPA1 to N910VVRU2CPD1: https://www.androidfilehost.com/?fid=24572369360126104
Flash N910VVRU2CQL1: (have not found this file yet)
I have a couple of questions about this:
Will this wipe the data on my phone (e.g. installed apps, settings, etc.)?
If so, is there any way to get to CQL1 without having to wipe my phone?
Am I missing anything?
Click to expand...
Click to collapse
follow here
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
Hi everyone, I've been a HTC10 owner for quite a while. When HTC decided to stop updates to Oreo, I decided to unlock the bootloader, flash a twrp and install some AOSP roms, based on Android 10, Android 11 and even Android 12, all found here on XDA. A few days ago I decided to put back the stock rom (with the flash method via sdcard) leaving the bootloader unlocked and S-ON. The flash is successful, the only thing that doesn't work anymore (it's not that it doesn't work, it doesn't detect it at all) is the fingerprint sensor (the option in the settings is missing). This happens both with Rom stock and with Rom on a sense basis. If, on the other hand, I flash a Custom Rom based on AOSP again, the sensor works again in an excellent way. What do you advise me to do? is there a way to flash the stock firmware with the whole rom? Like RUU? I accept any advice. I can do anything, the only thing I don't have is S-OFF.