Related
I am being plagued by wifi issues ever since i went to a new version of Purenexus. It seems to have something to do with going to 7.1.1
I've tried the older version of the rom that was working fine before, but i still seem to have wifi issues even in these older versions now.
i tried resurection remix, but still have the same issue.
after a while the wifi wont be connected and it says authentication problem, or sometimes shows it as simply discconected.
i can manually forget the network and re add it and it seems to work fine for a while.
Durring troubleshooting today, i have tried to resey my router, even upgraded the firmware,
anyways, i'd like to flash the factory image to test to see if i still have issues. but i want to make sure that if i install 7.1.1 factory image, or 7.0 that i can still re-flash twrp from adb or am i going to have to find a root exploit?
if i flash a factory image does it "relock" my bootloader? i guess that is the more important question
thanks.
citrusfizz said:
I am being plagued by wifi issues ever since i went to a new version of Purenexus. It seems to have something to do with going to 7.1.1
I've tried the older version of the rom that was working fine before, but i still seem to have wifi issues even in these older versions now.
i tried resurection remix, but still have the same issue.
after a while the wifi wont be connected and it says authentication problem, or sometimes shows it as simply discconected.
i can manually forget the network and re add it and it seems to work fine for a while.
Durring troubleshooting today, i have tried to resey my router, even upgraded the firmware,
anyways, i'd like to flash the factory image to test to see if i still have issues. but i want to make sure that if i install 7.1.1 factory image, or 7.0 that i can still re-flash twrp from adb or am i going to have to find a root exploit?
if i flash a factory image does it "relock" my bootloader? i guess that is the more important question
thanks.
Click to expand...
Click to collapse
There will be no locking of the bootloader unless you issue the command. No exploits needed. Just flash away...
Hi.
I'm just wondering if anybody can help me please?
I have a UK Huawei P9 EVA-L09 with Marshmallow currently on it (B166) build I think. It is unlocked and has TWRP 3.0.2.0 Recovery installed on it.
I would like to upgrade to Nougat 7.0 and EMUI 5.0, but most of my attempts have failed and I have had to use the rollback method to get back to Marshmallow.
I have tried to do it by flashing an Update.zip and subsequent EU_Apps package.zip through TWRP to no avail.
I have also tried the 'Dload' folder method, also to no avail. The closest I've gotten is to build no B378, but it shows up as NRD90M Test-Keys on the Build No in the phone settings instead and all apps such as camera, NFC, Bluetooth are missing / not working etc. Trying to then flash the EU_Apps package through 'Dload' method doesn't alleviate the problem of missing apps.
Does anybody have any tips for what I could try to get it onto a working Nougat build with apps please?
Also, if anybody has any links to any relevant firmware etc, then that would be very helpful too.
I'm pulling my hair our trying to get this to work. Surely it's can't be that hard can it??
Many thanks, Bill.
Is your phone branded? For a particular UK network I mean? And if so are you flashing ROMs for that network?
I don't know if that's the problem but I was on Vodafone UK B137 (which is Marshmallow) and flashed the 2 update zips for a Vodafone Nougat ROM thru TWRP and it was successful. I then flashed an updated zip using the "dload method" and that was successful too.
When you say you flashed the zips in TWRP "to no avail", what exactly was the end result?
Also might help if you give the full version of your starting ROM, and what zips you were trying to flash, ie full names and sources.
I'm kinda new to this device forum but seems like people get varying results with different flashing methods, for no particular reason either!
Peace.
chris5s said:
Is your phone branded? For a particular UK network I mean? And if so are you flashing ROMs for that network?
I don't know if that's the problem but I was on Vodafone UK B137 (which is Marshmallow) and flashed the 2 update zips for a Vodafone Nougat ROM thru TWRP and it was successful. I then flashed an updated zip using the "dload method" and that was successful too.
When you say you flashed the zips in TWRP "to no avail", what exactly was the end result?
Also might help if you give the full version of your starting ROM, and what zips you were trying to flash, ie full names and sources.
I'm kinda new to this device forum but seems like people get varying results with different flashing methods, for no particular reason either!
Peace.
Click to expand...
Click to collapse
Hi. Thanks for your reply.
When I tried to flash .Zips through TWRP it kept coming up with errors and didn't flash them (something about being umnable to mount /System).
I was on EE UK, but found a method yesterday for debranding my phone and setting it to C432. I also managed to successfully flash C432B182 firmware on it.
I have since attempted to flash Nougat B360 using the 'Dload' method and now my phone keeps asking me to enter my password to decrypt storage. Multiple attempts to reset my phone and wipe cache partitian don't seem to be working. Do you have any idea how I can get around this?
It's so hard and it's so annoying how other people seem to be getting it right and mine is proving to be a swine. Makes me want to get rid of it to be honest and get something easier.
Thanks again, Bill.
I'm concerned that this may be bricked right now. No amount of using eRecovery to reset the phone will stop it from going onto the dreaded 'enter password to decrypt storage' screen! I will see if I can re flash it using Fastboot, but I'm a bit concerned right now...
I have an O2 Branded one. I'm too chicken to mess with it in case I brick it!
Just waiting for the official UK O2 OTA update to arrive &
tmohammad said:
I have an O2 Branded one. I'm too chicken to mess with it in case I brick it!
Just waiting for the official UK O2 OTA update to arrive &
Click to expand...
Click to collapse
Probably advisable unless you absolutely know what you're doing and don't mind taking the risk. I'm a bit annoyed with Huawei and my carrier, they are always so slow with providing updates and Hmui 5.0 is only what Hmui 4.0 should have been in the first place. I'm done with these manufacturer's stupid over bloated overlays and will be going to an official Google phone in future!
If you can get it into fastboot mode, flash TWRP, then you should be able to progress from there, hopefully by at least formatting data to get rid of the encryption! Sounds like.a royal pita tho to be honest.
When I flashed to Nougat from MM using TWRP I got a bunch of error messages too, but it (eventually) booted up ok....
chris5s said:
If you can get it into fastboot mode, flash TWRP, then you should be able to progress from there, hopefully by at least formatting data to get rid of the encryption! Sounds like.a royal pita tho to be honest.
When I flashed to Nougat from MM using TWRP I got a bunch of error messages too, but it (eventually) booted up ok....
Click to expand...
Click to collapse
Hi again all.
Success! I finally managed to crack it.
I downloaded MM Firmware version C432B136 and used Huawei Extractor to extract the Boot.img, Recovery.img and System.img files and was able to boot into Fastboot mode fortunately. I used a Command Prompt to unlock the Bootloader again and flashed each .img file in line.
The phone booted up into the B136 firmware and I was then able to update OTA to B166, but not B182 strangely. So I downloaded a B182 version firmware and placed it in the 'dload' folder of the phone's S.D Card, before forcibly flashing it by holding volume up, volume down and the power button on boot up.
I subsequently used the below link, which showed me how to use Huawei Updater and HiSuite to update to B361 firmware.
https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2
Once on Nougat B361 firmware, my phone's update setting prompted me to update to the latest B378 firmware OTA.
Finally, to achieve Root status I followed the below guide and am now running root with SuperUser and BusyBox installed. I'm happy to report that both Nougat 7.0 and HMUI 5.0 are running smoothly on my phone and all features are working (i.e. Bluetooth, Camera and NFC) and performance and battery life are all noticeably better than ever.
https://forum.xda-developers.com/showpost.php?p=70927601&postcount=456
Be aware that my phone is EVA-L09, so I followed all guides and downloaded all firmware that related to my specific phone model.
Phew! Thanks for all of your help and good luck to those who are attempting to get this working.
Bill.
If i flash another, or update my rom (currently running openbeta 4 on 3t), alls ok until i flash su.
Then dm-verity on boot up reappears. I hate it.......
To rid of it i have to revert stock recovery. Sideload Os 4.1.1 or openbeta. But soon as i re-root with su im back with dm-verity error on bootup.
I can get rid again by process above and then flashing twrp and restoring a backup. Just means i cannot update or use another rom.
Ive just tried the [FIX] DM-Verity Warning (no flashing required)
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity doesnt work for me..
Is there a method in which it gets rid of this horrid problem once and for all. thanks in advance.
veroby said:
If i flash another, or update my rom (currently running openbeta 4 on 3t), alls ok until i flash su.
Then dm-verity on boot up reappears. I hate it.......
To rid of it i have to revert stock recovery. Sideload Os 4.1.1 or openbeta. But soon as i re-root with su im back with dm-verity error on bootup.
I can get rid again by process above and then flashing twrp and restoring a backup. Just means i cannot update or use another rom.
Ive just tried the [FIX] DM-Verity Warning (no flashing required)
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity doesnt work for me..
Is there a method in which it gets rid of this horrid problem once and for all. thanks in advance.
Click to expand...
Click to collapse
Flash the open beta, get rooted get set up etc. Flash the 4.0.2 firmware in TWRP then do the fastboot commands and then flash the open beta firmware in TWRP. Problem solved. The firmware files are found here
k.s.deviate said:
Flash the open beta, get rooted get set up etc. Flash the 4.0.2 firmware in TWRP then do the fastboot commands and then flash the open beta firmware in TWRP. Problem solved. The firmware files are found here
Click to expand...
Click to collapse
Just because im not a great fan of flashing firmware is this method something you have done or is there a thread on it. thanks for method
veroby said:
Just because im not a great fan of flashing firmware is this method something you have done or is there a thread on it. thanks for method
Click to expand...
Click to collapse
I did do this last night as I was greeted with the same Verity error after flashing the beta.
k.s.deviate said:
I did do this last night as I was greeted with the same Verity error after flashing the beta.
Click to expand...
Click to collapse
where did you find the method. Just a lucky guess or because you knew the fault is within the latest firmware.
Seems a little weird as the fastboot oem disable_dm_verity commands have only just come onto xda this morning. Seems weird because its working for most which would assume most are on 4.0.2 firmware. Meaning they havent update for a long time.
Updated - I have done your method and it has all worked out ok. Bonus my battery hasnt caught fire neither. Thankyou..:good:
veroby said:
where did you find the method. Just a lucky guess or because you knew the fault is within the latest firmware.
Click to expand...
Click to collapse
I searched for DM Verity error on op3t and got a few different threads dating back to the first firmwares. I've read before (and encountered before ) the issue on custom ROMs and open betas. So I knew where to look for the firmwares.
First I tried just using the fastboot commands and got no where, I knew the commands worked on the 4.0.2 firmware so I just flashed it, ran the commands and flashed the latest firmwares.
k.s.deviate said:
I searched for DM Verity error on op3t and got a few different threads dating back to the first firmwares. I've read before (and encountered before ) the issue on custom ROMs and open betas. So I knew where to look for the firmwares.
First I tried just using the fastboot commands and got no where, I knew the commands worked on the 4.0.2 firmware so I just flashed it, ran the commands and flashed the latest firmwares.
Click to expand...
Click to collapse
I have done your method and it has all worked out ok. Bonus my battery hasnt caught fire neither.:good: Thankyou..
veroby said:
I have done your method and it has all worked out ok. Bonus my battery hasnt caught fire neither.:good: Thankyou..
Click to expand...
Click to collapse
Glad my explanation helped.
Hi! Im thinkng to move from nexus 6 (not 6P) to 3T,and I have many, many, pet peeves, this would be one of them. Is this an issue with CM (now LineageOS) updates based roms? I mean, i understand that i'll have to remove it when first intalling another rom, but then if I update it, it'll trigger the warning again or not?. Thanks.
xtacb4 said:
Hi! Im thinkng to move from nexus 6 (not 6P) to 3T,and I have many, many, pet peeves, this would be one of them. Is this an issue with CM (now LineageOS) updates based roms? I mean, i understand that i'll have to remove it when first intalling another rom, but then if I update it, it'll trigger the warning again or not?. Thanks.
Click to expand...
Click to collapse
Don't think it does once u hv followed the steps above.
Not fully tested with me but if DM verity does persist it really is easy to remove. Advice is take the leap it's a great phone with the best support for any device i have ever owned.
veroby said:
Don't think it does once u hv followed the steps above.
Not fully tested with me but if DM verity does persist it really is easy to remove. Advice is take the leap it's a great phone with the best support for any device i have ever owned.
Click to expand...
Click to collapse
Hi, last message mine in this thread talking about this here, don't want to be offtopic, I purchased it yesterday, came home installed the usual (twrp[i love how fast the backups are made], CM14.1) and delivered the Nexus 6 to a friend (he bought it from me).
Thanks!
Hi guys, I have a OP3 which is running on 3.1.2 Marshmallow.
I always get a notification for system update to 4.5.1. I've tried downloading and installing the update but after the first boot my OP crashes/gets bricked. There is only a Linux penguin logo that appears no matter what button you press.
From there I always have to follow the mega unbrick guide and get my phone back to working with stock recovery and 3.1.2.
I've tried side loading the downloaded file as well.
Then I've tried installing .zip file of 5.0.1 via TWRP, still no luck. it still bricks my phone.
Am comfortable rooting my phone, my bootloader is unlocked. I don't care too much about keeping root after updating my phone to the latest version, I would be grateful to anyone who can point me towards the proper full ROM files of 5.0.1 along with any firmware files that may be required.
And the exact process of when to flash the firmware and with/without which version of TWRP. I am ready to completely wipe and clear data.
in simple words I just want to update from 3.1.2 to 5.0.1. The simple downloading and updateing from the OTA update doesn't work.
AbhiM7 said:
Hi guys, I have a OP3 which is running on 3.1.2 Marshmallow.
I always get a notification for system update to 4.5.1. I've tried downloading and installing the update but after the first boot my OP crashes/gets bricked. There is only a Linux penguin logo that appears no matter what button you press.
From there I always have to follow the mega unbrick guide and get my phone back to working with stock recovery and 3.1.2.
I've tried side loading the downloaded file as well.
Then I've tried installing .zip file of 5.0.1 via TWRP, still no luck. it still bricks my phone.
Am comfortable rooting my phone, my bootloader is unlocked. I don't care too much about keeping root after updating my phone to the latest version, I would be grateful to anyone who can point me towards the proper full ROM files of 5.0.1 along with any firmware files that may be required.
And the exact process of when to flash the firmware and with/without which version of TWRP. I am ready to completely wipe and clear data.
in simple words I just want to update from 3.1.2 to 5.0.1. The simple downloading and updateing from the OTA update doesn't work.
Click to expand...
Click to collapse
Try this: https://downloads.oneplus.com/oneplus-3/oneplus_3_oxygenos_5.0.1/
hellcat50 said:
Try this: https://downloads.oneplus.com/oneplus-3/oneplus_3_oxygenos_5.0.1/
Click to expand...
Click to collapse
Hi, I've already downloaded this very stable file and tried flashing using TWRP
AbhiM7 said:
Hi, I've already downloaded this very stable file and tried flashing using TWRP
Click to expand...
Click to collapse
I read something about wrong batteries causing this problem. Do you use the original battery?
hellcat50 said:
I read something about wrong batteries causing this problem. Do you use the original battery?
Click to expand...
Click to collapse
I though of running a diagnosis check by dialing *#808# and looked up Charger option, it shows the battery as "itech_3000mah"
is that original?
I had given the phone to repair for water damage to a professional service chain (Not OnePlus, some company here called Yaantra). I've heard from talking to an official repair person of OnePlus that fake batteries are not possible for OnePlus.
The battery works absolutely alright, charges up nicely and I get decent SOT. Can't complain at all.
Ok, so let me start this off by saying I feel kind of dumb right now. I am really new to all this.
I bought a motog5s, and rooted it with super su.
I tried to add a different OS rom (several actually).
I ended up messing up somehow and deleting my backup of the stock rom which I nandroid saved on twrp-3.1.1-sanders.img
I now have a phone with no Operating Sytem. I had twrp-3.1.1-sanders.img and tried to upgrade to twrp-sanders-r2.img which worked but, deleted my backup of stock rom install when i deleted the internal storage like a moron, also didn't help me install a rom w/o error messages so then I upgraded to twrp-sanders-r16.img, which worked also. But now I get error 7 every time I try to install any rom.
Right now my phone has just twrp-sanders-r16.img and no operating system.
How do I resolve the error 7 and error 255(i was getting earlier but now just error 7), and install an operating system? I wanted to get pixel experience working which was what got me all turned around in the first place. I also tried Cosmic, Arrow, AOSPext all of which where in the XDA roms forum(for Moto G5S, Sanders) but kept getting error 255 then I tried to do a fix (deleted assert command from a file in the rom with text editor, but kept saying my ZIP files weren't the proper format, I have ubuntu linux on my computer...which should work) and it stopped giving error 255 and now gives error 7.
I have tried sidebooting, and also many different roms and all give errors. I also had lots of trouble with Open Gapps/larger files/Roms when trying to download on my cpu and then move/copy to my phone's internal storage so I don't know how to resolve that either.
I now want to get a solid rom OS on here ( that's noob friendly) and root with magisk of which i have DL'd 16.0 & Magisk Manager 5.8.3 (last stable release i think)
How do I fix this? Please help!
thank you very much for any help in advance.
First off make sure you have a Moto G5s Plus not the smaller variant. If it's a Plus, than fastboot flash this twrp recovery and try downloading a fresh ROM, gapps, and also Magisk. Flash those guys and you should be good.
Sent from my XT1806 using Tapatalk
treyweez11 said:
First off make sure you have a Moto G5s Plus not the smaller variant. If it's a Plus, than fastboot flash this twrp recovery and try downloading a fresh ROM, gapps, and also Magisk. Flash those guys and you should be good.
Sent from my XT1806 using Tapatalk
Click to expand...
Click to collapse
when i try to flash the rom i get error 7 and it won't install.
mr_moneroj said:
when i try to flash the rom i get error 7 and it won't install.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=890129502657595739
Sorry meant to put this link to update twrp. See if this version will clear you of the error
Sent from my XT1806 using Tapatalk
treyweez11 said:
https://androidfilehost.com/?fid=890129502657595739
Sorry meant to put this link to update twrp. See if this version will clear you of the error
Sent from my XT1806 using Tapatalk
Click to expand...
Click to collapse
Awesome, I will give it a go. Appreciate your help. Thank you.
treyweez11 said:
https://androidfilehost.com/?fid=890129502657595739
Sorry meant to put this link to update twrp. See if this version will clear you of the error
Sent from my XT1806 using Tapatalk
Click to expand...
Click to collapse
Ok I flashed TWRP R20 and it's now on my phone.
I tried flashing Lineage OS, got error 7.
Tried flashing the version of Lineage OS where I deleted the assert code from the beginning of the Updater-Script (which was supposed to fix it.) Instead, I get an error saying it's an improperly formatted zip file.
What solution can I try for resolving this error 7? It happens with every single rom I try.
mr_moneroj said:
Ok I flashed TWRP R20 and it's now on my phone.
I tried flashing Lineage OS, got error 7.
Tried flashing the version of Lineage OS where I deleted the assert code from the beginning of the Updater-Script (which was supposed to fix it.) Instead, I get an error saying it's an improperly formatted zip file.
What solution can I try for resolving this error 7? It happens with every single rom I try.
Click to expand...
Click to collapse
Just try a fresh downloaded room
Sent from my XT1806 using Tapatalk
kinda' haven't rooted except for other ppl much in the past decade, but i just did this phone and from what i understand, first of all flashing magisk on top of supersu seems like a bad idea since they alter complely different directories. pretty sure you'd want to stick with one or the other unless you reverted to stock first. other than that, did you reformat your system partition on the first try? did you wipe before trying other roms?
stuck with same error.
stuck with exact same error 7, did you got any solution, plz send if any, thank you
xt1804
mr_moneroj said:
Ok, so let me start this off by saying I feel kind of dumb right now. I am really new to all this.
I bought a motog5s, and rooted it with super su.
I tried to add a different OS rom (several actually).
I ended up messing up somehow and deleting my backup of the stock rom which I nandroid saved on twrp-3.1.1-sanders.img
I now have a phone with no Operating Sytem. I had twrp-3.1.1-sanders.img and tried to upgrade to twrp-sanders-r2.img which worked but, deleted my backup of stock rom install when i deleted the internal storage like a moron, also didn't help me install a rom w/o error messages so then I upgraded to twrp-sanders-r16.img, which worked also. But now I get error 7 every time I try to install any rom.
Right now my phone has just twrp-sanders-r16.img and no operating system.
How do I resolve the error 7 and error 255(i was getting earlier but now just error 7), and install an operating system? I wanted to get pixel experience working which was what got me all turned around in the first place. I also tried Cosmic, Arrow, AOSPext all of which where in the XDA roms forum(for Moto G5S, Sanders) but kept getting error 255 then I tried to do a fix (deleted assert command from a file in the rom with text editor, but kept saying my ZIP files weren't the proper format, I have ubuntu linux on my computer...which should work) and it stopped giving error 255 and now gives error 7.
I have tried sidebooting, and also many different roms and all give errors. I also had lots of trouble with Open Gapps/larger files/Roms when trying to download on my cpu and then move/copy to my phone's internal storage so I don't know how to resolve that either.
I now want to get a solid rom OS on here ( that's noob friendly) and root with magisk of which i have DL'd 16.0 & Magisk Manager 5.8.3 (last stable release i think)
How do I fix this? Please help!
thank you very much for any help in advance.
Click to expand...
Click to collapse
I think ! you should trying " Back to Stock Rom by XDA"
regarding back to stock rom
Sanjay.it said:
I think ! you should trying " Back to Stock Rom by XDA"
Click to expand...
Click to collapse
is back to stock rom have anything do with recovery changes
i made some changes in team-win recovery and while flashing some commands giving errors is that a problem with my pc system
and can i downgrade to 7.1.1 firmware, previously i was on 8.1 june 2018
any reply is appreciated, thank you
I had a similar problem. While trying to flash liquid_remix ROM I kept getting error 7. I checked and saw that my system partition was not mounted in TWRP. After mounting it the ROM flashed fine.
solved this issue on my moto g5s plus
mr_moneroj said:
Ok, so let me start this off by saying I feel kind of dumb right now. I am really new to all this.
I bought a motog5s, and rooted it with super su.
I tried to add a different OS rom (several actually).
I ended up messing up somehow and deleting my backup of the stock rom which I nandroid saved on twrp-3.1.1-sanders.img
I now have a phone with no Operating Sytem. I had twrp-3.1.1-sanders.img and tried to upgrade to twrp-sanders-r2.img which worked but, deleted my backup of stock rom install when i deleted the internal storage like a moron, also didn't help me install a rom w/o error messages so then I upgraded to twrp-sanders-r16.img, which worked also. But now I get error 7 every time I try to install any rom.
Right now my phone has just twrp-sanders-r16.img and no operating system.
How do I resolve the error 7 and error 255(i was getting earlier but now just error 7), and install an operating system? I wanted to get pixel experience working which was what got me all turned around in the first place. I also tried Cosmic, Arrow, AOSPext all of which where in the XDA roms forum(for Moto G5S, Sanders) but kept getting error 255 then I tried to do a fix (deleted assert command from a file in the rom with text editor, but kept saying my ZIP files weren't the proper format, I have ubuntu linux on my computer...which should work) and it stopped giving error 255 and now gives error 7.
I have tried sidebooting, and also many different roms and all give errors. I also had lots of trouble with Open Gapps/larger files/Roms when trying to download on my cpu and then move/copy to my phone's internal storage so I don't know how to resolve that either.
I now want to get a solid rom OS on here ( that's noob friendly) and root with magisk of which i have DL'd 16.0 & Magisk Manager 5.8.3 (last stable release i think)
How do I fix this? Please help!
thank you very much for any help in advance.
Click to expand...
Click to collapse
hii, mr_moneroj
i was having the same error
and back to stock rom worked for me,
let me find links that could lead you to solve problem
https://forum.xda-developers.com/mo...ockrom-android-8-1-oreo-oficial-twrp-t3804750
means i did this, hope works for you
first i restored my phone through this backup
then my network and fingerprint were not working well
so used this you tube video
follow this instructions after above link restore
https://youtu.be/iu3BOs7nMuA
very well explained, follow them
i did this and back to stock also i got official 8.1 right now, upgrading
bye....