I'm on 6.0 Marshmallow XT1575 and my wifi toggles off on its own
Things I've tried to fix this:
-factory reset
-flash non-hlos.bin modem
-flash boot.img from here:
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
-restore nandroid backup from before the error
-a wipe then a flash of 6.0 stock from here:
http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
-use the return to stock tool from a different post to return to 5.11 from here:
http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905
I'm on 6.0 Marshmallow with the may security update. I decided to do a dirty flash of 6.0 Marshmallow to get rid hidesu and return my phone to stock. I did the flash and booted my phone, but my lockscreen refused to unlock. Every time I did the right code it would lock again. I factory reset and was able to login, but wifi was stuck off, and sim card was not being recognized. From other posts here, I flashed modem and now my sim card access was restored, but wifi is still broken. I've since tried everything on the list above, but nothing brings back wifi. Any ideas?
Also, not sure if this is normal, but on my phone info I see the Wi-Fi MAC address as
02:00:00:00:00:00
which does not seem right to me
EDIT:
Honestly did not expect it to work, but I flashed a custom ROM, TruPureXMM 2.9, and now my wifi is back. I think I'll stick with it for a while.
The problem was with custom kernel you probably installed. I had the same problem with it.
So i was flashing Hydrogen Os v2.5 through twrp and since 20 mins the .zip file did not flash so i switched off the phone and when i tried re-installing h2os v2.5 it was again taking longer to flash so i turned the phone off again and this time i installed oxygen os v3.1.0 ,for sometime the phone was in bootloop but when it booted there was no wifi, no network and i found that my phone had no imei number plus unknown baseband, unknown bluetooth also i don't have an efs backup can anyone help me restore my phone to normal once again?
point here.
phorcus said:
So i was flashing Hydrogen Os v2.5 through twrp and since 20 mins the .zip file did not flash so i switched off the phone and when i tried re-installing h2os v2.5 it was again taking longer to flash so i turned the phone off again and this time i installed oxygen os v3.1.0 ,for sometime the phone was in bootloop but when it booted there was no wifi, no network and i found that my phone had no imei number plus unknown baseband, unknown bluetooth also i don't have an efs backup can anyone help me restore my phone to normal once again?
Click to expand...
Click to collapse
Same happened with me phone doesn't boot... Can't install recovery...
Nothing works tried all possible ways like hard reset
what recovery are you guys using?
---------- Post added at 03:26 AM ---------- Previous post was at 03:24 AM ----------
This version works with TWRP 302.2, make sure you are using that.. DO NOT use stock recovery..
---------- Post added at 03:32 AM ---------- Previous post was at 03:26 AM ----------
The ideal way to flash h2os is, flash the rom, flash the debloater, dont flash gapps at all.. boot into the rom, the first boot takes a lot of time so dont worry as long as the phone is not rebooting again and again.. once it boots up go through the setup, dont use oneplus account, then install the google installer apk..
https://www.techmesto.com/install-hydrogen-os-google-apps-oneplus-2/
then follow the procedure written in this link to install gapps.. and you're done.. you can use h2os 2.5 now!
Reverting back to OOS 3.1, I have not tried myself.. Maybe, get into recovery (twrp) do a factory reset first after going into wipe, then go into advanced wipe, wipe everything EXCEPT internal storage.. then flash OOS 302 instead of OOS 3.1, and see if it working with all the connectivity. THIS PROCEDURE IS NOT TESTED BY ME!!
As far as I know, the current oxygen version does not support the latest modem.. So you have two options..
1) install HOS again and like the above method use as it is
2) install HOS again to regain the networks(don't install gApps) and then using latest twrp, do a clean install of cm14.1 official.. But cm14.1 official with the latest modem is highly unstable if you use the mobile network..
My recommendation is to stick to the beta version of HOS for a few days and continue using it if you like it or flash cm14.1 once a stable build supporting the newer modem comes.. And when the updated oxygen OS comes in this or the next month, you can install it!
zipalign said:
point here.
Click to expand...
Click to collapse
thank you for your help so i was on mokee 7.1 when i flashed only this hydrogen modem v1.1 and when i booted i did not find any volte option, so i went back to latest twrp recovery and tried flashing h2os v2.5 but since 20 minutes i was seeing this ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png ) so i switched off my phone midway and then i installed oxygen os v3.1.0 although it got into a boot loop but when it booted there was no wifi, no imei no, no baseband and many more and when i tried installing mokee or cm14.1 again although they got flashed but when i booted my device i saw oneplus logo and for a few seconds i also saw cm logo and the device continuously kept rebooting in a loop also i am only able to flash oxygen os v3.1.0 that too with no wifi, no imei etc. whereas cm14.1 and mokee wouldnt even boot but they do get flashed and h2os wouldnt even flash , please help :crying:
shravansp24 said:
As far as I know, the current oxygen version does not support the latest modem.. So you have two options..
1) install HOS again and like the above method use as it is
2) install HOS again to regain the networks(don't install gApps) and then using latest twrp, do a clean install of cm14.1 official.. But cm14.1 official with the latest modem is highly unstable if you use the mobile network..
My recommendation is to stick to the beta version of HOS for a few days and continue using it if you like it or flash cm14.1 once a stable build supporting the newer modem comes.. And when the updated oxygen OS comes in this or the next month, you can install it!
Click to expand...
Click to collapse
thanks for writing out, but i am unable to flash H2OS it is taking forever to install, it just says " patching system image unconditionally " i tried installing it through latest twrp and i tried hybrid recovery too
Rohandd said:
what recovery are you guys using?
---------- Post added at 03:26 AM ---------- Previous post was at 03:24 AM ----------
This version works with TWRP 302.2, make sure you are using that.. DO NOT use stock recovery..
---------- Post added at 03:32 AM ---------- Previous post was at 03:26 AM ----------
The ideal way to flash h2os is, flash the rom, flash the debloater, dont flash gapps at all.. boot into the rom, the first boot takes a lot of time so dont worry as long as the phone is not rebooting again and again.. once it boots up go through the setup, dont use oneplus account, then install the google installer apk..
https://www.techmesto.com/install-hydrogen-os-google-apps-oneplus-2/
then follow the procedure written in this link to install gapps.. and you're done.. you can use h2os 2.5 now!
Reverting back to OOS 3.1, I have not tried myself.. Maybe, get into recovery (twrp) do a factory reset first after going into wipe, then go into advanced wipe, wipe everything EXCEPT internal storage.. then flash OOS 302 instead of OOS 3.1, and see if it working with all the connectivity. THIS PROCEDURE IS NOT TESTED BY ME!!
Click to expand...
Click to collapse
i am using twrp-3.0.2-2-oneplus2.img but h2os takes forever to install, but i did flash h2os v2.5's modem v1.1 before flashing h2os v2.5.
i am also seeing this message in twrp " Failed to mount /system (invalid argument) " please help guys
Flashing h2os does take more time than usually flashing other roms.. maybe 10 mins or so.. but not 20-25 mins.. and ideally 302.2 should work with h2os without any issues.. I am using that right now.. i can boot into recovery and everything.. I'm not really sure what is the problem here now..
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
shravansp24 said:
As far as I know, the current oxygen version does not support the latest modem.. So you have two options..
1) install HOS again and like the above method use as it is
2) install HOS again to regain the networks(don't install gApps) and then using latest twrp, do a clean install of cm14.1 official.. But cm14.1 official with the latest modem is highly unstable if you use the mobile network..
My recommendation is to stick to the beta version of HOS for a few days and continue using it if you like it or flash cm14.1 once a stable build supporting the newer modem comes.. And when the updated oxygen OS comes in this or the next month, you can install it!
Click to expand...
Click to collapse
I did return to cm14.1 by seraph after flashing h2os.. and i did not experience any random reboots with mobile data on 4g.. im using vodafone and idea..
Rohandd said:
Flashing h2os does take more time than usually flashing other roms.. maybe 10 mins or so.. but not 20-25 mins.. and ideally 302.2 should work with h2os without any issues.. I am using that right now.. i can boot into recovery and everything.. I'm not really sure what is the problem here now..
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
I did return to cm14.1 by seraph after flashing h2os.. and i did not experience any random reboots with mobile data on 4g.. im using vodafone and idea..
Click to expand...
Click to collapse
I didnt try the seraph build.. Will try it! Thank you
phorcus said:
thanks for writing out, but i am unable to flash H2OS it is taking forever to install, it just says " patching system image unconditionally " i tried installing it through latest twrp and i tried hybrid recovery too
Click to expand...
Click to collapse
Yeah itll show that message and will last for 5-10mins.. Hydrogen is very slow to install.. If it lasts longer, try flashing the recovery again and trying it..! Or directly flash cm14.1 to see if its booting
Rohandd said:
Flashing h2os does take more time than usually flashing other roms.. maybe 10 mins or so.. but not 20-25 mins.. and ideally 302.2 should work with h2os without any issues.. I am using that right now.. i can boot into recovery and everything.. I'm not really sure what is the problem here now..
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
I did return to cm14.1 by seraph after flashing h2os.. and i did not experience any random reboots with mobile data on 4g.. im using vodafone and idea..
Click to expand...
Click to collapse
can you please check this screenshot ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png )
shravansp24 said:
I didnt try the seraph build.. Will try it! Thank you
Yeah itll show that message and will last for 5-10mins.. Hydrogen is very slow to install.. If it lasts longer, try flashing the recovery again and trying it..! Or directly flash cm14.1 to see if its booting
Click to expand...
Click to collapse
i reflashed the recovery and installed cm14.1 but then the device gets into boot loop,what's the problem here?
phorcus said:
i reflashed the recovery and installed cm14.1 but then the device gets into boot loop,what's the problem here?
Click to expand...
Click to collapse
Even i got into a bootloop after flashing RR or cm14.1.. Dont know the exact issue..
But installing the new h2os, booting it and then clean flashing cm14.1 solved the bootloop issue..!
shravansp24 said:
Even i got into a bootloop after flashing RR or cm14.1.. Dont know the exact issue..
But installing the new h2os, booting it and then clean flashing cm14.1 solved the bootloop issue..!
Click to expand...
Click to collapse
can you tell me the steps you followed to install h2os? cause when i am installing it, it takes forever to install like i waited for almost 20 mins before giving up, or should i wait more?
and did you get the same message as i got like " failed to mount /dev/block/bootdevice........and so on..... device or resource busy "
check the screenshot here ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png )
phorcus said:
can you tell me the steps you followed to install h2os? cause when i am installing it, it takes forever to install like i waited for almost 20 mins before giving up, or should i wait more?
and did you get the same message as i got like " failed to mount /dev/block/bootdevice........and so on..... device or resource busy "
check the screenshot here ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png )
Click to expand...
Click to collapse
1) Got into recovery
2) wipe-advanced wipe-everything except internal storage
3) install-HOS rom
(took around 5 minutes)
4) boot rom and finish initial setup
5) Got into recovery
6) wipe-advanced wipe-everything except internal storage
7) install-cm14.1 rom + gapps
8) boot
Maybe your rom is corrupt, try redownloading and im using latest twrp
shravansp24 said:
1) Got into recovery
2) wipe-advanced wipe-everything except internal storage
3) install-HOS rom
(took around 5 minutes)
4) boot rom and finish initial setup
5) Got into recovery
6) wipe-advanced wipe-everything except internal storage
7) install-cm14.1 rom + gapps
8) boot
Maybe your rom is corrupt, try redownloading and im using latest twrp
Click to expand...
Click to collapse
Thank a lot Bro that worked like a charm the downloaded file was corrupt but i got only one network and i am still on h2os, did you get both networks on cm 14.1?
phorcus said:
Thank a lot Bro that worked like a charm the downloaded file was corrupt but i got only one network and i am still on h2os, did you get both networks on cm 14.1?
Click to expand...
Click to collapse
I got both networks to work in cm14.1 but theyre extremely unstable.. I have my phone in flight mode most of the time to avoid reboots.. Wifi works fine.. The moment you activate the sim, it depends on your luck then.. Mine worked 10mins, sometimes 15, then reboots, again 5-10mins and again reboot(tried official as well as seraph's)
shravansp24 said:
I got both networks to work in cm14.1 but theyre extremely unstable.. I have my phone in flight mode most of the time to avoid reboots.. Wifi works fine.. The moment you activate the sim, it depends on your luck then.. Mine worked 10mins, sometimes 15, then reboots, again 5-10mins and again reboot(tried official as well as seraph's)
Click to expand...
Click to collapse
everything is back to normal on my phone, actually i visited the service center today and they told me that my phone is dead and that i would need to pay 17k to change the motherboard :laugh:
problem here is that H2OS 2.5 messed up all our modems, and who has not made OOS EFS backup via terminal is in trouble now.
when problem popped up in all forums [XDA, and OnePlus one mainly] there have been proposed several solutions, like flashing H2OS modem .zip via recovery, after installing OOS.
so now many users have different scenarios to approach, and a working allwide solution seems not to be found 'til now.
personally I have official TWRP 3.0.2-2 and all my flashings have been made with it.
started from OOS 3.1.0 I had on my phone in the last week, 100% working, then flashed H2OS 2.5. seen the new ROM, decided to get back to something more familiar, so I wiped all and flashed latest nightly of CM13. it was working like a charm, but I had bluetooth issues with my xiaomi mi band [like I always had with OP2 and CM13], so I decided to flash back OOS 3.1.0 wiping data.
OOS 3.1.0 booted up, but without connectivity.
then I realized my modems have been messed up, and started looking for a solution.
the only one I'd try is to fastboot flash OOS 3.0.2 .zip [kindly uploaded by Spannaa], and see if my phone starts working again like it should.
'til now, I will stay with H2OS 2.5 which works perfectly. but when I have time, I'll empty my phone backupping all my stuff [fastboot flashing the .zip mentioned above will wipe userdata too, so I'd lose all my stuff] and try the fastboot thing [I already did it a few months ago, no issues at all].
for those who are in big trouble, that cannot flash anything from recovery, I'd suggest to try to fastoboot flash OOS 3.0.2 with the .zip linked above.
if this solution still doesn't come to an happy ending, then you have to try with the unbrick tool from Qualcomm and see what will happen.
the most important thing is and always will be: don't do anything until you are not aware of what you're actually doing to your phone.
Hello,
I'm facing the following issue:
I updated my android to 9.0 through recovery using a flashable stock zip. After that I followed all instructions and wiped the system to flash the last Resurrection Remix rom (January).
I was having signal issues, then I read that maybe flashing the modem could help me (January update because is the only one for Pie):
https://forum.xda-developers.com/mi-a1/themes/twrp-baseband-modem-april-stock-rom-t3777901
So I did it all again (flashed the stock, wiped the system, flashed RR and then flashed the modem - all through TWRP), but well, here I am...
I'm really enjoying RR and would like to keep it.
Is there some way to solve this? I already tried to use Network Signal Guru but it didn't solve my problem.
I'm from Brazil and my network carrier is 'Claro'
PS: I found this link on RR thread, in the "Vendor and Boot images", there's a 'signal boost' zip there but I don't know if it may brick my phone 'cause maybe it only works with Android 8, and even if it works I don't know how to flash vendor zip.
https://sourceforge.net/projects/resurrectionremix-oreo/files/tissot/treble-aio/
Thank you
Device: ZB602KL 4gb
I was using the latest Liquid Remix 10.0.6 with the stock darkonah kernel for a wee after having just updated from LR 10.0.5 and Singh 2.7. When I noticed he released a stable update for his kernel to 2.8 I downloaded it and flashed it as normal. Upon booting into LR, the lockscreen no longer responded to my fingerprint. It wasn't even turning the screen on. After inputting my password, I noticed that my wifi wouldn't turn on. And later when I tried the stock gcam, it kept crashing. Cam2API Probe is completely blank.
Things I've done to try and fix this:
1. Rebooted multiple times.
2. Someone suggested wiping /system and /vendor only and dirty flashing the rom. Did that, dirty flashed LR, openGApps(wasn't sure I needed to, did it anyway), and Magisk 19.
3. Clean flashed stock 340, decrypt and magisk19.
4. Flashed fw_only-X00T-WW-16.2017.1902.037.zip. I had previously flashed fwpie050.zip(the one from opendesktop) when updating LR before all this happened.
5. Fully wiped phone including internal storage and flashed the latest HavocOS which I am on right now as I've given up and just need it to work as a phone for the meantime.
Camera seems to be working again on Havoc, though. Fingerprint is still missing from Security settings and WiFi will not turn on.
Any help would be appreciated. Thanks!
I also got bootloop by using magisk 19.0,use magisk 17.1 or 18.1.
How did you clean flash stock 340 ? If it was through TWRP then try fastboot ROM
Tianhe said:
How did you clean flash stock 340 ? If it was through TWRP then try fastboot ROM
Click to expand...
Click to collapse
Yes, through twrp. What are the adb commands to do it through fastboot? I used Avinash's modified stock340 btw.
I think the modem firmware is corrupted somehow. I cannot receive or make calls but can get 4g data connection and SMS. My wifi mac address sometimes is "Uknown" or 02:00:00:00:00:00.
defurious said:
Yes, through twrp. What are the adb commands to do it through fastboot? I used Avinash's modified stock340 btw.
I think the modem firmware is corrupted somehow. I cannot receive or make calls but can get 4g data connection and SMS. My wifi mac address sometimes is "Uknown" or 02:00:00:00:00:00.
Click to expand...
Click to collapse
Flash fastboot stock rom it will fix the issue.
https://forum.xda-developers.com/as...ow-to/guide-revert-to-stock-rom-lock-t3798420
Hit thanks if it helped
Flashing stock rom thru adb basically reverts your phone to factory state so everything should be fixed unless somehow your hardware is damaged
farhanshaikh671 said:
Flashing stock rom thru adb basically reverts your phone to factory state so everything should be fixed unless somehow your hardware is damaged
Click to expand...
Click to collapse
Yeah, i understand. I'm just a little confused because the steps in the linked post above are for 334. I don't know how to do it using 340. Should I just follow those steps then after relocking, manually update to 340, and then unlock bootloader again?
Is there any way to flash fastboot rom without relocking bootloader?
To me it seems that i'm having some problems with pie beta firmware. After flashing 339 and then LR 10.0.5 which is the last version before requiring pie beta firmware, everything is working normally again. But as soon as i try to update to 10.0.6 or latest Havoc with pie beta firmware, the wifi and fpsensor stop functioning. But the strange thing is, I was on LR 10.0.6 for a week before flashing Singh 2.8 kernel which then killed my hardware.
Now I'm wondering if I should just wait for official Pie release from Asus.
defurious said:
Yeah, i understand. I'm just a little confused because the steps in the linked post above are for 334. I don't know how to do it using 340. Should I just follow those steps then after relocking, manually update to 340, and then unlock bootloader again?
Is there any way to flash fastboot rom without relocking bootloader?
To me it seems that i'm having some problems with pie beta firmware. After flashing 339 and then LR 10.0.5 which is the last version before requiring pie beta firmware, everything is working normally again. But as soon as i try to update to 10.0.6 or latest Havoc with pie beta firmware, the wifi and fpsensor stop functioning. But the strange thing is, I was on LR 10.0.6 for a week before flashing Singh 2.8 kernel which then killed my hardware.
Now I'm wondering if I should just wait for official Pie release from Asus.
Click to expand...
Click to collapse
Just Flash Stock rom via fastboot to fix this issue. Dont bother about bootloader getting relocked.( U may unlock it ri8 after flashing)
And one more thing.
If u flash Decrypt.zip used for Stock Oreo roms on Stock Pie, you will loose wifi and fingerprint options.(I experimented this thoroughly)
So flash decrypt.zip for pie on Pie Stock(Beta or Stable).
Tested personally and worked fine.:good:
Hit thanks if it helped,
akhil850 said:
Just Flash Stock rom via fastboot to fix this issue. Dont bother about bootloader getting relocked.( U may unlock it ri8 after flashing)
And one more thing.
If u flash Decrypt.zip used for Stock Oreo roms on Stock Pie, you will loose wifi and fingerprint options.(I experimented this thoroughly)
So flash decrypt.zip for pie on Pie Stock(Beta or Stable).
Tested personally and worked fine.:good:
Hit thanks if it helped,
Click to expand...
Click to collapse
This must be the problem then because I didn't know there was a decrypt for pie beta and i usually do flash decrypt coz i have a phobia that my internal data will get encrypted with no password to recover. ?
Can you provide a link for pie beta decrypt please? I can't find it here in xda. Thanks
defurious said:
This must be the problem then because I didn't know there was a decrypt for pie beta and i usually do flash decrypt coz i have a phobia that my internal data will get encrypted with no password to recover. ?
Can you provide a link for pie beta decrypt please? I can't find it here in xda. Thanks
Click to expand...
Click to collapse
Here https://forum.xda-developers.com/as...w-to/decrypt-zip-asus-stock-pie-roms-t3923265
Hit thanks if i helped.
ok i'm in need of help from the experts. I have a few lex727 zl1's that i've been using with lineage for a while now and all has been well until I upgraded (was running a 14.1 nightly on one of the phones, no firmware update). When I attempted to install lineageos 16. I got the modem assert error from
Code:
twrp: assert(leeco.verify_modem("2017-01-06 01:40:06") == "1")
which from looking on these forums means i needed to upgrade my firmware. so I grabbed the latest twrp and the latest firmware from here: link
download zl1 727 30s and 20s from here
applied the firmware update by booting into fastboot and running each flash individually: which I did by following this
Fired up recovery, 16 install went fine this time. gapps, blah blah. phone booted up and looked good but my cell connection is pretty much always dead. when it connects, it does so for a very small amount of time then dies again
I'm in the US on ting
If I take my sim out and put it back in my old zl1 with the old setup, everything goes back to working perfectly. LTE+ and stable connection
Is there something I'm missing? Did I not flash something correctly?
Any help would certainly be appreciated. Thx
Did you try to back up /system from your old zl1 and flash to one which does not work to see if it works as you expect? Jus to rule out a hardware problem?
Also why didn't you download the firmware from LineageOS site? https://wiki.lineageos.org/devices/zl1/
Recovery: https://twrp.me/leeco/leecolepro3.html