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 have a d851. I had a fully functional Marshmallow AOSP ROM backed up. Installed N&N Rom 8.0 Beta (Stock) which had 30e. Had no signal. Went back to my AOSP rom. Now SIM card is not detected. Never had this problem before. It only happened after installing this rom. Any help?
N&N (from htcm... forum) do not have beta versions. The rom is "UPDATE N&N 8.0 G5 ULTIMATE ROM", an update for N&N G5 ULTIMATE ROM.
This rom is only for D855: [D855]UPDATE N&N 8.0 G5 ULTIMATE ROM (30E ~ 6.0 Marshmallow)
if you've installed on a D851 it is normal to have failures
They have a d851 port. I been running their rom before but this is the first time having this problem. Also it is a full rom with an "update only" option.
Right, i know. I just wanted to distinguish the port and the original rom, which is only for d855.
Greetings
I have tried flashing the 30d modem but still no luck. In every rom i try to restore there is no baseband and i checked the IMEI and its blank. I have an EFS restored back when I was on lollipop roms. I have also downloaded stock marshmallow rom. My question is, once I flash this, I wlll lose root but will still have TWRP, how do i re obtain root? Also, I was on Lollipop when I originally rooted my phone, which took forever, does that affect how I can fix this problem?
I'm an idiot who just assumed that the unlocked phone he bought new in Europe was the European version (dual-SIM) and didn't first take a backup of all the partitions before messing around with it.
I'm wondering if I got sold some other region's hardware by a shady seller. How can I tell? Do I just have to flash every firmware out there until I get it to boot, or is there another way?
Model: XT1635-02
Type: M1D64
And dual-SIM.
I unlocked the bootloader, flashed TWRP, decided that I wanted to take the OTA, reflashed recovery to stock from the latest EU package...and it would no longer boot. Flashed back to TWRP, same. Reflashed the entire firmware package following these instructions, but it still won't boot.
Thanks.
--
Update: after considerable fiddling, I reloaded TWRP and got it to install and boot the Cyanogenmod 14.1 release, meaning my device is not permanently trashed beyond repair-- it just doesn't like any of the firmwares I've tried to feed it. Obviously this is still sub-optimal since CM requires some blobs that Moto haven't yet released to support the camera etc., but it's better than nothing. My goal is still to get stock firmware back onto this phone.
Update2: buoyed by my CM14.1 success, I decided to try to apply a similar methodology to get the stock firmware running. I failed utterly. Maybe if I build a TWRP-flashable copy of the stock RETEU package I could get it to flash fully and boot, but all it does at this point is loop over the bootloader unlock warning screen and occasionally attempt to auto-erase itself in Recovery before bootlooping again.
Update3: aaaand my IMEI is "0." This seems bad.
boot to fastboot screen and take a pic of it and post it.
Hello there,
Preamble:
Since first wave of OTAs came out, I've been wondering about going back to stock to get one. But yesterday I noticed that LeeDroid ROM got an update to Oreo (5.00), so I decided to try that out first.
Well, I failed – the installation process went just fine, however I failed to boot. That's when I thought of going back to LeeDroid 4.00 – wiped everything as instructed and installed the previous version. And now my radio doesn't work.
Question:
Could this radio problem be caused by 8.0 ROM installation even though I had Nougat firmware?
And what should I do to resolve this problem?
Thanks in advance!
The same problem. here
if you find a solution, please tell me, i have exactly the same problem
That's why you are REQUIRED to have Oreo firmware for any Stock or custom Oreo stock based roms.
Upgrading to Oreo will result in loss of baseband upon downgrading back to Nougat.
(new boot.img/ramdisk places firmware bits in places that the old boot.img/ramdisk doesn't see)
There currently is no method to update and then go back.
Your only available solution, is to fully update to Oreo firmware and software to get your baseband back.
There are already several threads which discuss this in pretty great lengths and detail.
santod040 said:
That's why you are REQUIRED to have Oreo firmware for any Stock or custom Oreo stock based roms.
Upgrading to Oreo will result in loss of baseband upon downgrading back to Nougat.
(new boot.img/ramdisk places firmware bits in places that the old boot.img/ramdisk doesn't see)
There currently is no method to update and then go back.
Your only available solution, is to fully update to Oreo firmware and software to get your baseband back.
There are already several threads which discuss this in pretty great lengths and detail.
Click to expand...
Click to collapse
So, essentially I need to flash Taiwanese RUU and 8.0 OTA now to get things work?
(My device is TW as well)
Elegiacal said:
So, essentially I need to flash Taiwanese RUU and OTA now to get things work?
(My device is TW as well)
Click to expand...
Click to collapse
Correct! :good:
I'll keep this quick. I was playing a game on my a520f and it froze. I rebooted and got the message that only original firmware can be flashed.
Tried to reinstall the latest original stock rom, but instead of the one that came with lots of bloatware from the provider, i flashed the ZTO variance.
Long story short, now everytime i boot, it starts to use more and more ram until it crashes, and my IMEI has gone to ****.
PLEASE HELP
Ive tried the sidesync emergency restore, but the phone dont show on the list.
Edit1: I cant flash the stock bootloader because of the U3 BL from the january security patch. AND KNOX WAS TRIPPED.
Edit2: MANAGED TO SOLVE. To anyone that have the same Problem: Re-flash the exact same Stock Rom that your phone came with. The bootloader needs to be U3 if you have the January 2018 Security Patch
hi! I have this problem but my bootloader is U4
DaniPS2002 said:
hi! I have this problem but my bootloader is U4
Click to expand...
Click to collapse
Try reinstaling the Stock rom that came with your phone, specifically the same Bootloader.
For me, it was trying at least 4 roms until i flashed the very one that came with the phone, and i mean the provider version.
Hope it helps
Can someone give me an backup of the efs partiton with twrp of a520f please?