Hi,
I recently installed stock Nougat on my phone after being on LineageOS for some time. After installing, I noticed that I no longer had LTE or any data whatsoever. I can still connect to cell service, send texts, etc, but no data. At this point I'm desperate to get data so please let me know what I need to do to get back a data connection. I want to try installing a ROM on it to see if it's just a stock Nougat problem, but I'm nervous about that as I've heard it causes problems with the Nougat modems. Any advice?
How did you install the stock Nougat ROM? Via fastboot from the thread in my signature? If so, you need to do it again because the radio flash failed... if some other way, you likely have a kernel/radio mismatch causing this issue. Marshmallow radios are not compatible with the Nougat kernel, and Nougat radios are not compatible with the Marshmallow kernel.
Related
Hello! Recently T-Mobile launched MM 6.0.1 for the Galaxy Note 4. I was originally running CM Remix, that was meant for the international version of this device, and all but sim card did not work, (I don't have this device activated, I just use it on the side). When I got bored of the CM Remix I just went to Samsung Kies, and restored the phone to its factory default. When I finished setting up the phone I was pleased to find that I was running 6.0.1, as opposed to 5.1.1. All good? No! I have used Odin to put on the latest version of TWRP recovery, and i flashed v2.76 of SuperSU. All works well in terms of rooting and flashing files, but here is my big issue. NO MATTER WHAT rom that I flash on this damn phone, wifi doesnt work, nor do the service bars show I have signal. I have flashed 6 different roms, and all of them have to same issue, stock 4.4.4, 5.0, 5.11 CM 12,12.1 13, Ressurection Remix. The only thing holding me together is my TWRP nandroid backup that i revert to after every rom I flash. In settings, my phone just says "Turning wifi on" and it stays there. SO WHAT THE @#$% IS GOING ON? Is this something T-MObile implemented when it did the update on my N4, I restored to 5.1.1 with kies all the time before this and after each time, i flashed roms with no issue. Can someone please point me in the right direction here, am I doing something wrong? Is something patched that wasn't previously? WHAT CAN IT BE?
Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.
CritKlepka said:
Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.
Click to expand...
Click to collapse
I recommend you install this one instead:
https://forum.xda-developers.com/ve...m-1-85-605-9-aroma-root-root-debloat-t3529732
Follow instructions in OP...or:
1)fastboot flash FW w/o Boot w/ TWRP (htc_fastboot oem rebootRUU, fastboot flash zip...)
2)htc_fastboot reboot-bootloader
3) Finally, go into recovery-- backup and flash ROM (choose root w/ Magisk and debloat)
Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.
CritKlepka said:
Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.
Click to expand...
Click to collapse
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware
Antny6 said:
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware
Click to expand...
Click to collapse
I have been doing a lot of searching, but I've found so many different, conflicting sources of information. For example, one website told me to install LineageOS, was to be on latest Verizon OTA and just normally flash it; that obviously didn't work.
So from what I can see, our choices are Viper, Ice, LeeDroid, NuSense and the one you linked. I'm going to try out LeeDroid... out of curiousity, is there any reason, for example, LeeDroid or Ice haven't posted in this Verizon section with links to their ROMs?
*Edit Two* Dialer wouldn't work out of the "box" so to speak, so I had to go to Phone settings at the bottom, there is a menu called Calling Accounts. Had to go there and tap Receive Incoming Calls... why is that disabled in the first place..? But that seems to be an issue going even as far back as the Nexus 5. But that's how you find the option in the HTC 10 for anyone who comes across this issue too...
Not sure why your having issues with the flashing. Are you doing a full wipe? Not just factory reset. Going from stock to lineage requires a complete format of internal SD card. On the stock roms, most will ask if you are still on marshmallow firmware & are working fine. Again, we need more info on what firmware version your on, version of twrp& how your wiping your device. Most AOSP roms work, but no advanced calling
LOS ROMs will work without issue IF you have flashed the US unlocked firmware at some point in time. This is the only information that we have found from a VzW device with LOS booting and VzW device without. We started a thread awhile ago and is the only known method we currently know of to get LOS booting. Also works for Sprint users.
https://forum.xda-developers.com/verizon-htc-10/how-to/how-to-cm-booting-vzw-vzw-firmware-t3500900
I had custom roms installed on my device but decided to go back to stock rom. I was able to restore the stock rom, updated and installed twrp and root on my device. I noticed that after I did this, my headphone jack stopped working and my PC doesn't detect my phone for USB file transfer or MTP configuration anymore (on stock, rooted). I wanted to know if I have the same problem on custom rom so I flashed a custom rom and both issues are resolved. Although I liked the Custom roms I tried (Havoc OS and Arrow OS Pie), I decided to go back to stock again this morning because one particular game that I'm playing (Mobile Legends) isn't working properly on custom roms (screen would sometimes flicker or go into black screen, I didn't experience this on stock). This time I decided to forget about root and relock my bootloader. After updating, I ran into the same problem with my headphone jack and usb file transfer. Does anyone have the same problem? If so, how did you get the headphone jack and usb file transfer to pc working again? Please help. Thanks.
I am facing the same problem ! anyhow installed lesser and switching between speakers and headphones ! Usb still isn't working !
romi7 said:
I am facing the same problem ! anyhow installed lesser and switching between speakers and headphones ! Usb still isn't working !
Click to expand...
Click to collapse
The only way I could use usb file transfer is when I boot into a custom recovery. I went back custom rom for now, until I find a permanent solution for both. I tried searching for answers at the Zentak forums but couldn't any help there.
Have you tried flashing the raw firmware first than update? It's here somewhere on unofficial unlock/re-lock post, I went back to stock ROM after re-lock without any issues. I did have an issue flashing using AFT after re-lock, but flashing corresponding recovery.img than flash firmware using recovery solved that.
sanctitude888 said:
Have you tried flashing the raw firmware first than update? It's here somewhere on unofficial unlock/re-lock post, I went back to stock ROM after re-lock without any issues. I did have an issue flashing using AFT after re-lock, but flashing corresponding recovery.img than flash firmware using recovery solved that.
Click to expand...
Click to collapse
'
Hi! Thank you! My problem is now fixed, both headphone jack and USB file transfer, although I'm not really sure if it will work for others. What I did was I flashed (while device is unlocked) the Nougat raw firmware (WW_ZE552KL_14.2020.1712.85_M3.10.47.15), tested it and both were functioning. I decided to update to Oreo using the system update feature and it is still now working after I installed all the Oreo updates. I'm not planning to re-lock anytime soon as I installed root and found it beneficial.
I did follow the unofficial unlock/ re-lock prior to doing the previous steps, although I first flashed the factory raw rom (CSC_ZE552KL_13_13_1_36_M2_6_7_P7_userdebug.zip), unlocked and the flashed the Oreo raw firmware (WW_ZE552KL_15.0410.1806.68_M3.10.47.19) . Maybe skipping to flash the Nougat Raw firmware caused the problem? I'm not really sure, sorry I'm relatively new to all these.
Glad to know it's all ok on your part
borutosdad said:
'
Hi! Thank you! My problem is now fixed, both headphone jack and USB file transfer, although I'm not really sure if it will work for others. What I did was I flashed (while device is unlocked) the Nougat raw firmware (WW_ZE552KL_14.2020.1712.85_M3.10.47.15), tested it and both were functioning. I decided to update to Oreo using the system update feature and it is still now working after I installed all the Oreo updates. I'm not planning to re-lock anytime soon as I installed root and found it beneficial.
I did follow the unofficial unlock/ re-lock prior to doing the previous steps, although I first flashed the factory raw rom (CSC_ZE552KL_13_13_1_36_M2_6_7_P7_userdebug.zip), unlocked and the flashed the Oreo raw firmware (WW_ZE552KL_15.0410.1806.68_M3.10.47.19) . Maybe skipping to flash the Nougat Raw firmware caused the problem? I'm not really sure, sorry I'm relatively new to all these.
Click to expand...
Click to collapse
Yup you should flash Oreo RAW as custom ROMs (Android 8 and above) needs latest modem.
Hey all......I created a thread awhile back when I borked my phone trying out a new treble rom that was supposed to be so easy even a nOOb could flash it, and it ended up messing up my phone to the point where the only way for me to get it back was to follow the thread to disassemble the phone and short the chip out.
Then, the screen was not responsive on ANY rom I flash except for MM and it worked with any up to B29. I tried a few times to upgrade all in vain but I was always able to flash MM B29 and have it work again.
Flash forward to last night and my itchy trigger upgrade finger did it again and I attempted to flash the Oreo from ZTE. It flashed fine but, again, no responsive screen. I thought well, maybe I could try Nougat again and I flash many different versions and in different ways (used miFlash, EDL tool, MiFavor recovery, twrp) and all resulted in the screen not being responsive. Sigh, so I flashed MM B29 but now it will not detect any sim or even allow wifi to be turned on.
I have tried multiple times to reflash MM B29 using all the different ways above and even went back and forth between roms. I tried the original way most of us first unlocked the bootloader and flashed through all those stepped zip packages from B20 to B29 and still nothing. I finally used twrp to erase/format all data and made certain the partitions were formatted as ext4 and tried again, still no sim.
I realize that my imei is not showing and even tried a program to flash? that to the phone.
NOW, what needs to be said is during ALL of this flashing the phone signal/sim DID show......yes.......the sim DID WORK......when I flashed anything other than MM B29. LOL. Of course, the issue is none of those roms allow the screen to work.
Please, if anyone can help I would appreciate it very much. I'm thinking by flashing the Oreo from ZTE it may have changed something that the MM B29 rom is not changing to allow the phone to read the imei/sims.
I'm not sure but I think the DFU multitool posted by @raystef66 can fix the IMEI issue.
You have installed the correct modem for you device? EG: if you've flashed a U modem on a G device the sim and WiFi won't work.
If this is correct check APN and network setting in the phones software.
I hope this helps ?
Syberclone said:
I'm not sure but I think the DFU multitool posted by @raystef66 can fix the IMEI issue.
You have installed the correct modem for you device? EG: if you've flashed a U modem on a G device the sim and WiFi won't work.
If this is correct check APN and network setting in the phones software.
I hope this helps
Click to expand...
Click to collapse
I appreciate the suggestions. Unfortunately, the DFU tool doesn't seem to work for me as it remains listed as Disconnected even after choosing the correct port.
I have always flashed the MM B29 EDL rom (A2017U_B29_MARSHMALLOW_FULL_EDL) that contains the correct modem. As I said, it always worked before.
As far as checking APN/network settings, well, there are none to check because the sim is not detected so all of those choices are greyed out. The signal bars fr both sims are blank in the notification area and of course wifi does not turn on.
I just finished another round of trying different roms to flash including LOS 15. LOS came up to the welcome screen (just like all the others) AND the AT&T logo with LTE full signal bars showing. Again, the screen does not respond to touch so it's all useless. I am at a loss as to why flashing MM B29 is no longer working for me.
Stop using guides mentioned in Axon7 thread,or stop listening to other users.Only thing i see here are bricks.
Probably you have hardware fault
The Axon 7 has been the worst phone for being bricked.
I've flashed ROMs on HTC's, Motorola and Google phones all without problems.
There are way too many packages and bootstacks etc, etc that cause problems and confusion.
So I wouldn't say don't follow threads or users advice.
My advice is research, research and research some more.
Thanks for the suggestions.
Something to get clear.....
I can successfully flash the roms and get to the Welcome screen to begin setup.
MARSHMALLOW:
-screen does respond to touch
-sims are NOT detected
-no AT&T logo
-no phone signal
ANY OTHER VERSION (Nougat, Oreo):
-screen does NOT respond to touch
-sims are recognized
-AT&T logo appears
-phone signal strength meter shows full bars
So, it's not a hardware fault. The phone was working perfectly fine when I had Marshmallow flashed. It's only this last time I flashed the Oreo from ZTE's website and when that did not work I tried a few other roms and then went back to the Marshmallow B29 EDL that I had been using all along.
Isn't there a way to COMPLETELY wipe this phone and start from scratch? As in, when your Windows is so full of crap and running slow you can format the hard drive and reinstall Windows from scratch. I have tried TWRP and format data (have to type yes to format) etc........is there a way to format w=everything that might affect the sim from being detected in Marshmallow? Better yet, the screen from being responsive in other ROMS after marshmallow?
djprez said:
Thanks for the suggestions.
Something to get clear.....
I can successfully flash the roms and get to the Welcome screen to begin setup.
MARSHMALLOW:
-screen does respond to touch
-sims are NOT detected
-no AT&T logo
-no phone signal
ANY OTHER VERSION (Nougat, Oreo):
-screen does NOT respond to touch
-sims are recognized
-AT&T logo appears
-phone signal strength meter shows full bars
So, it's not a hardware fault. The phone was working perfectly fine when I had Marshmallow flashed. It's only this last time I flashed the Oreo from ZTE's website and when that did not work I tried a few other roms and then went back to the Marshmallow B29 EDL that I had been using all along.
Isn't there a way to COMPLETELY wipe this phone and start from scratch? As in, when your Windows is so full of crap and running slow you can format the hard drive and reinstall Windows from scratch. I have tried TWRP and format data (have to type yes to format) etc........is there a way to format w=everything that might affect the sim from being detected in Marshmallow? Better yet, the screen from being responsive in other ROMS after marshmallow?
Click to expand...
Click to collapse
Did you installed a vendor partition?
Predatorhaze said:
Did you installed a vendor partition?
Click to expand...
Click to collapse
I am not certain. If the Oreo update that I downloaded directly off the ZTE site has one, then yes. If that is the cause, how would I modify it?
@djprez: To my knowledge, ZTE's official B12/B20 do not have a vendor partition. ZTE will almost certainly never add Treble support for the A7, if they are going to do so then now is an ideal time, since the A7 is an end-of-life device and no longer being manufactured.
I finally give up. I had lineage 15.1 running on the device and decided to upgrade to a pie based rom. So I flashed november firmware, rom etc. then I only had 3g. Now I decided maybe I need to flash latest december firmware so I flashed the 10.0.3 firmware zip and lost my sim card completely. I reflashed the november firmware. This made the device bootloop so I decided to flash stock november rom again and start all over. Now it's independent of the rom it's running it boots until the sim pin dialog, i can even press some numbers but it just reboots after a certain amount of time. Access to fastboot works fine so any idea how I could fix this would be greatly appreciated.
Looks like you got a corrupted EFS partition. If you have a TWRP backup for that, just restore. And if you don't, there is a thread in the Mi A1 forum about restoring EFS when downgrade from Pie.
Benjamin_L said:
I finally give up. I had lineage 15.1 running on the device and decided to upgrade to a pie based rom. So I flashed november firmware, rom etc. then I only had 3g. Now I decided maybe I need to flash latest december firmware so I flashed the 10.0.3 firmware zip and lost my sim card completely. I reflashed the november firmware. This made the device bootloop so I decided to flash stock november rom again and start all over. Now it's independent of the rom it's running it boots until the sim pin dialog, i can even press some numbers but it just reboots after a certain amount of time. Access to fastboot works fine so any idea how I could fix this would be greatly appreciated.
Click to expand...
Click to collapse
First of all try to disable SIM Pin Lock from another phone. It was a bug from previous releases.
Second: never downgrade from Pie because it will causes issues and potential corruption.
jack_21 said:
First of all try to disable SIM Pin Lock from another phone. It was a bug from previous releases.
Second: never downgrade from Pie because it will causes issues and potential corruption.
Click to expand...
Click to collapse
But is downgrading from a custom rom comparable? And the firmware zips only have modems and bootloaders don't they? I am always struck how difficult the a1 is compared to my pixel 2
Benjamin_L said:
But is downgrading from a custom rom comparable?
Click to expand...
Click to collapse
Well, you upgraded to 10.0.3.0 so you must use only that Pie firmware for now