Hello Guys,
I am not getting any network after flashing my phone with hydrogenos and flashing back to CM12.
- As required , i had to install chinese TWRP recovery to install hydrogen os.
- After running the hydrogen os for couple of hours i decided to go back to CM12
- Flashed TWRP latest one and flashed CM12 using TWRP recovery.
- As Cyanogen does not support installing OTA updates using TWRP i flashed CM12 original recovery.
- The phone turned on just fine but without any network.
- Then i tried to flash back to stock CM11S but the phone got bricked.
- I followed a tutorial and restored back it to CM11S.
Even after doing all these i am still getting "No service" but the name of operator is showing.
Pls help
try flashing the appropriate modem along with the stock ROM
Related
so i flashed the lolli img from google and all was fine. wanted to install a custom rom so i flashed the latest twrp and then cataclysm. all seemed well but when i turned off wifi i just get the no service error, its on LTE and seems correct. then i tried to go back into recovery and it just reboots. i had slimlp rom on there and the same thing happened with the recovery problem.
any help? just want to keep the recovery working and get the cell radio all fixed with cataclysm
People with TWRP 2.8.2.0.might need to.downgrade to 2.8.1.0.
The latest version hangs at the curtain if it has MTP enabled.
I've used CM12.1 based ROMs for a while now, and with my talent have managed to brick my bacon (oneplus one global 64GB), and unbrick it (using this guide)
I've restored it to stock with no problem using this tool.
my problem begins when i try to update to any LP ROM - flashing such ROMs' zip files in TWRP returned "E: error executing updater binary in zip". i found two solutions to this error:
1. first one is described in this thread. i ditched this method after it got me stuck in bootloop every time after flashing a ROM
2. second one (probably the way it should be done) is to update device firmware like described in this oneplus forums thread. flashing this zip indeed allowed me to successfully install my ROM but with one big problem - the SIM card is detected for a few seconds (even then the device wont find any networks) and then drops to "no SIM card detected - emergency calls only" then it gets detected again and so on...
I've also tried flashing some different modems like described here but it didn't change anything
have anyone encountered any network related problem after upgrading to a CM12.1 based ROM or have any idea how to solve my problem (mobile network connections won't function after upgrading to cm12 firmware)?
help would be very appreciated!
edit: if it helps, i also found that OTA updating to the latest build XNPH44S also breaks the phone's ability to connect to a mobile network
Get the oneplus one build which was released as a fix to ghost touch.. It is nothing but oxygenOS!! Backup ur data and follow the instructions and flash the oxygen rom then wait for the first boot after first boot just update ur recovery to latest twrp and get the bacon firmware update zip file from any of the major rom threads like blisspop or exodus then flash that then flash the latest cm12.1 nightly and AK kernel(optional) then boot it up!!!
Transmitted via Bacon
yashshan said:
Get the oneplus one build which was released as a fix to ghost touch.. It is nothing but oxygenOS!! Backup ur data and follow the instructions and flash the oxygen rom then wait for the first boot after first boot just update ur recovery to latest twrp and get the bacon firmware update zip file from any of the major rom threads like blisspop or exodus then flash that then flash the latest cm12.1 nightly and AK kernel(optional) then boot it up!!!
Transmitted via Bacon
Click to expand...
Click to collapse
1. TWRP must be installed before installing OxygenOS as it comes as a flashable zip and not an OTA/Cyanodgen update...
2. installing OxygenOS was no problem without the firmware, however after it booted i noticed it broke my mobile communications in a very similar way, so no luck with that one.
3.even after installing oxygen the firmware update is required to install anything like a CM nightly or a CM based LP ROM, and my problem was that this firmware upgrade broke my network connection, so i don't see how that could help me in any way
3.1 after flashing OxygenOS not even the firmware update would allow me to install a different ROM...
4. i linked the forum thread my firmware update came from (also found a similar suggestion in a YouTube video) and couldn't find any reference to it in any of the main ROMs' threads like you suggested, they all just say to install TWRP wipe everything and flash their zip (some say to flash a nightly before)
any other ideas? I'm starting to get desperate around my suddenly not-so-functional bacon :crying:
!!SOLVED!!
steps:
1. flash the latest CM12S fastboot image
2 .delete line 2 "aassert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1");" from the updater-script file in the custom ROM's ZIP installation file
3. flash the "hacked" zip file with no problem
4. enjoy your custom ROM installed bacon, WITH your mobile connection.
thanks for the help anyway!
Hey, so i formatted the boot partition by accident today and could not boot anymore.
I was on a 5.1.1 Custom ROM before that. So i googled a bit and found a fix by flashing the Stock Firmware. Downloaded a 4.4.4 Stock Firmware here (RETAIL-DE) and flashed it using the commands here (as described in 3b). The second command failed with "Preflash validation failed". I believe thats because i had bootloader version 4.1.19 already and its not possible to flash an older one over that.
After that i could boot the phone again into the Stock Android 4.4.4. So i wanted to go back to an Lollipop or Marshmallow ROM. Using fastboot i flashed the latest TWRP Recovery and used it to flash a Custom ROM. I've tried several ROMs but every ROM results in an bootloop. Also tried using TWRP 2.6.0.0 and 2.7.0.0, but it didnt change sth.
I hope someone can help me solving this issue. Thanks.
You should probably full-flash the latest original Motorola firmware (GPE 5.1 or stock 5.0.2) before putting TWRP and custom roms based on Android L or M.
Hi guys,
Not sure if anyone else has had this issue, but I've only got a Moto G 4G fairly recently (my Nexus 5 died) and have been attempting ROM flashing (never had an issue with multiple Nexus phones & tablets) I was flashing the rom OK but the sim card wasn't recognised - so went back to rooted stock Kitkat & Xposed.
Today I thought I'd give it another go, got into TWRP, advanced wipe as usual...but it didn't complete and the phone suddenly booted back into the system (with the Android upgrading/optimizing message you usually get when starting a new phone)
System is untouched, still rooted/xposed etc. Does anyone have an idea why this has suddenly happened? Never encountered anything like this before. TWRP is the latest version 3.1.1.0
Any suggestions welcome, cheers.
Just thinking....would flashing with adb be a solution?
Just flash lollipop stock ROM using mfastboot
later you can flash twrp recovery and then proceed with the nougat or oreo based ROM.. Bootloader should be updated so my suggestion is flash lollipop stock ROM
I am having a problem installing customs ROM on stock LG G2. My phone was bricked so I reverted to stock AT&G firmware using LG flash tool (Android version - 4.4.2, Kernel version - 3.4.0).
I then perform the following steps:
(1) Enable developer mode with USB debugging
(2) Use Kingo Root to root phone
(3) Install TWRP using AutoRec
(4) Update TWRP to latest version (3.2.1)
This is where the problems start. I get the same result when I try installing crDroid 7.1.2 or Resurrection Remix 5.7.4 custom ROMs.
The installation of the custom ROM (and gapps) succeeds in TWRP and then I reboot the system. However, the reboot always results in the "LG" logo showing for 1/2 seconds and then a constant black screen.
I am able to recover the phone from this by putting it into firmware update and then using LG Flash tool however I would still like to successfully install and use the custom ROMs. Not sure why this is happening (I am sure it might have been treated with in the forums however I cant find anything). Any help would be appreciated here as I really do not want to be stuck on stock AT&T firmware.
Update
randyesh said:
I am having a problem installing customs ROM on stock LG G2. My phone was bricked so I reverted to stock AT&G firmware using LG flash tool (Android version - 4.4.2, Kernel version - 3.4.0).
I then perform the following steps:
(1) Enable developer mode with USB debugging
(2) Use Kingo Root to root phone
(3) Install TWRP using AutoRec
(4) Update TWRP to latest version (3.2.1)
This is where the problems start. I get the same result when I try installing crDroid 7.1.2 or Resurrection Remix 5.7.4 custom ROMs.
The installation of the custom ROM (and gapps) succeeds in TWRP and then I reboot the system. However, the reboot always results in the "LG" logo showing for 1/2 seconds and then a constant black screen.
I am able to recover the phone from this by putting it into firmware update and then using LG Flash tool however I would still like to successfully install and use the custom ROMs. Not sure why this is happening (I am sure it might have been treated with in the forums however I cant find anything). Any help would be appreciated here as I really do not want to be stuck on stock AT&T firmware.
Click to expand...
Click to collapse
Update: It seems as if older ROMs can be installed with no issues. I got a copy of Cyanogen 12 and it installed perfectly and works fine. However, trying to install new ROMs still give issues. Don't know if I am missing something here and/or someone had a similar previous experience.