Hi folks, I've tired to get back into roms today after a few years absence. I've tried 3 roms on my 6P but ResurrectionRemix and Dirty Unicorns won't find any wifi. Cataclysm which I installed in between the two did. RR is also telling me 'theres an internal problem with your device'. I've wiped the normal things and even done a full format. Any ideas?!
Edit: just tired Bliss and that does work?! But I'm getting an error about a vendor image being out of date?
rendez2k said:
Hi folks, I've tired to get back into roms today after a few years absence. I've tried 3 roms on my 6P but ResurrectionRemix and Dirty Unicorns won't find any wifi. Cataclysm which I installed in between the two did. RR is also telling me 'theres an internal problem with your device'. I've wiped the normal things and even done a full format. Any ideas?!
Edit: just tired Bliss and that does work?! But I'm getting an error about a vendor image being out of date?
Click to expand...
Click to collapse
If you even tried reading op of rom threads, you would realise that you have an outdated vendor image. In order for wifi to work on latest roms and get rid of that message, flash latest vendor image ending with "x" and youll be fine. You can flash it in twrp
Thanks. I did flash MTC19X_vendor and I still get the message though?
rendez2k said:
Thanks. I did flash MTC19X_vendor and I still get the message though?
Click to expand...
Click to collapse
Then the rom you flashed wasnt updated recently and isnt using latest vendor
feis said:
Then the rom you flashed wasnt updated recently and isnt using latest vendor
Click to expand...
Click to collapse
OK, thanks. So how do I know which to flash?
rendez2k said:
OK, thanks. So how do I know which to flash?
Click to expand...
Click to collapse
I have done a bit of research, apparently the vendor image has to be up to date with the ROM but the problem is if I get the ROM dirty unicorn I could not find any vendor image for their ROM version 10.4 latest one. I don't understand whats happening with the system but this WiFi problem has recently occurred to many people.
unknowndeveloper said:
I have done a bit of research, apparently the vendor image has to be up to date with the ROM but the problem is if I get the ROM dirty unicorn I could not find any vendor image for their ROM version 10.4 latest one. I don't understand whats happening with the system but this WiFi problem has recently occurred to many people.
Click to expand...
Click to collapse
Flash the Vendor.img for the July security update. Dirty Unicorns 10.4 uses this vendor file. I download the entire factory image each month from Google Nexus factory page and flash what I need. I'm running July DU on my Nexus 5X with no WiFi issues.
https://developers.google.com/android/nexus/images?hl=en
Sent from my Nexus 5X using Tapatalk
Related
OK guys. Before you bite my head off, I'm an experienced ROM flasher and a junior ROM developer....I've been rooting every phone/tablet I get, I know how to use adb/fastboot and even made a personal stock ROM....like I said....junior not an expert lol....I currently have a nexus 5,6,7(2013). Now, I will be getting my new nexus 6p gold 32gig tomorrow (Tuesday). I have read about the new /vendor partition. Since I ha e never had to deal with that, I need your help. Any info about it before I root it tomorrow would be much appreciated!!!
From my understanding is that it contains the propitiatory drivers, libraries, and such, but what I found out creating my ROM is that it does not contain all of them. If you decide to create your own ROM from AOSP, then I can help you with it.
dl200010 said:
From my understanding is that it contains the propitiatory drivers, libraries, and such, but what I found out creating my ROM is that it does not contain all of them. If you decide to create your own ROM from AOSP, then I can help you with it.
Click to expand...
Click to collapse
So, flashing ROMs and such....I don't have to mess with vendor?
Just if there is a newer version out. I think now u can flash the vendor. Img via twrp 3.0 if I'm not wrong
jamescable said:
So, flashing ROMs and such....I don't have to mess with vendor?
Click to expand...
Click to collapse
Depending on the ROM, sometimes you do. If you have previously been using a Layers theme for example, you'd need to flash the vendor partition when flashing a new ROM otherwise the data well carry across (Layers resides in the vendor partition).
Heisenberg said:
Depending on the ROM, sometimes you do. If you have previously been using a Layers theme for example, you'd need to flash the vendor partition when flashing a new ROM otherwise the data well carry across (Layers resides in the vendor partition).
Click to expand...
Click to collapse
Is it correct that twrp does this job now in 3.0?haven't tried for myself yet
pa.pn2 said:
Is it correct that twrp does this job now in 3.0?haven't tried for myself yet
Click to expand...
Click to collapse
From what I've seen posted, yes. I haven't tried it myself though.
Heisenberg said:
From what I've seen posted, yes. I haven't tried it myself though.
Click to expand...
Click to collapse
I guess you are talking about flashing the Vendor image itself - not a flashable version of the vendor ? (probably a dumb question but I thought clarification for me and any other who might be confused couldnt hurt?)
jamescable said:
So, flashing ROMs and such....I don't have to mess with vendor?
Click to expand...
Click to collapse
Only time I flash the vendor is when updating to the latest of the ROM I use. Also going to the latest vendor factory img from google in the process. And like the other guy said when going from a layers ROM to anything else.
mocsab said:
I guess you are talking about flashing the Vendor image itself - not a flashable version of the vendor ? (probably a dumb question but I thought clarification for me and any other who might be confused couldnt hurt?)
Click to expand...
Click to collapse
Yes that's right.
as of 3.0.0-0 you can flash vendor and system images in twrp
Hey everyone. I have an interesting issue. I recently updated my phone to 7.0, but have ultimately decided to give it a bit more time to mature before hopping over. I flashed back the vendor for the September 6.0.1 image, and flashed the latest DU. However, on boot, I am still getting the vendor popup. I double-checked the build number on the ROM, and it is the correct image. I also flashed back the MTC20L bootloader and radio, but am still getting the error. What exactly am I doing wrong? Am I stuck with this vendor error on boot until I flash back to 7.0?
stompysan said:
Hey everyone. I have an interesting issue. I recently updated my phone to 7.0, but have ultimately decided to give it a bit more time to mature before hopping over. I flashed back the vendor for the September 6.0.1 image, and flashed the latest DU. However, on boot, I am still getting the vendor popup. I double-checked the build number on the ROM, and it is the correct image. I also flashed back the MTC20L bootloader and radio, but am still getting the error. What exactly am I doing wrong? Am I stuck with this vendor error on boot until I flash back to 7.0?
Click to expand...
Click to collapse
Have you checked when the last DU was updated. Guessing it was August, but their forum should tell you if it's the L or the F build. Personally, I'd go back to MM stock first, but ...
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
Have you checked when the last DU was updated. Guessing it was August, but their forum should tell you if it's the L or the F build. Personally, I'd go back to MM stock first, but ...
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
There is a 09/09 build that is 20L. I ultimately did just that, though. Back on 6.0.1 with no problems. Just gotta go through everything again. Thanks again!
EDIT: I am an idiot. It is F and not L. Reflashed to stock and continued to get the error. Flashed the correct vendor and I am back. Pretend this didn't happen.
Hi all,
I am new to the Axon 7 community and hopefully this isn't a silly question. I have not seen anything to really explain this - maybe its out there and I missed it.
I see many threads on getting a custom recovery loaded on the phone. In some of them, the TWRP image linked is from the TWRP site (twrp.me) and other times the NetHunter site (nethunter.com). Why would I use a TWRP image from NetHunter and not from TWRP themselves?
Thanks for setting me straight
user7743 said:
Hi all,
I am new to the Axon 7 community and hopefully this isn't a silly question. I have not seen anything to really explain this - maybe its out there and I missed it.
I see many threads on getting a custom recovery loaded on the phone. In some of them, the TWRP image linked is from the TWRP site (twrp.me) and other times the NetHunter site (nethunter.com). Why would I use a TWRP image from NetHunter and not from TWRP themselves?
Thanks for setting me straight
Click to expand...
Click to collapse
Use whichever you like, both work
Just be careful about the version, versions lower than 3.1.0 are dangerous and backing up stuff can wreck your phone
Does that mean it is just a case of someone else built the code then rather than being a modification to the code?
user7743 said:
Does that mean it is just a case of someone else built the code then rather than being a modification to the code?
Click to expand...
Click to collapse
Maybe it is a mirror... can't test but you could compare md5
Understood. I mostly wanted to understand if it was forked for one reason or another. It would appear not.
user7743 said:
Understood. I mostly wanted to understand if it was forked for one reason or another. It would appear not.
Click to expand...
Click to collapse
well there are more than one TWRP versions out there it seems. For example when you flash the universal bootloader TWRP displays 3.1.0-N while on stock 7.1 it shows 3 1.0-0
I've got a little issue myself, twrp installed via add 3.1.0.0 it works I've flashed roms and worked perfectly even though there's no official build for our A7 but yes everything works as it should. OK I backed up 3 backups the original rom and resurrection remix official and Tesla rom they all worked and flashed perfectly using twrp. But 2 of these backups will not restore it fails saying no partition selected but the original rom will back up no problem. And help guys this is the first time I've run into this. I've tried doing via the axon 7 tool also. Thanks in advance.
fastjohnson said:
I've got a little issue myself, twrp installed via add 3.1.0.0 it works I've flashed roms and worked perfectly even though there's no official build for our A7 but yes everything works as it should. OK I backed up 3 backups the original rom and resurrection remix official and Tesla rom they all worked and flashed perfectly using twrp. But 2 of these backups will not restore it fails saying no partition selected but the original rom will back up no problem. And help guys this is the first time I've run into this. I've tried doing via the axon 7 tool also. Thanks in advance.
Click to expand...
Click to collapse
The problem I think is data partition.
Every time I swich rom to oficial I have to format data, wipe dont work. Maybe before restore format data in f2fs or ext4 for oficial rom
Enviado desde mi ZTE A2017G mediante Tapatalk
May sound strange but it was because I flashed the ROM and gapps from my USB c style flash drive so I just decided to do the phone over fresh. It's working 100% all fresh install. Thanks for your help but no matter what I did it wasn't going to install those restores.
Happy New Year everyone!
I am out of ideas, I hope you could help me. I tried to flash and install Lineage OS on my Moto X Style.
Unlocking bootloader went fine, I installed new TWRP 3.2.1.0 and so far it was OK. I flashed LineageOS nightly from 25 Dec with GApps but it won't boot. I have booting animation and from time to time there is very short vibration, just fraction of a second every 3-4 sec. I left the phone for an hour, still stuck on booting animation. I tried to wipe data/cache, tried several other builds from December- all have the same issue. I proceed to other ROMs, all behave in the same way, infinite bootloop. I went to find some solutions on XDA, but nothing seems to work.
I tried restore from backup: https://forum.xda-developers.com/moto-x-style/general/nougat-stock-rom-moto-x-style-xt1572-t3718460 Did not work, I still had booting animation form Lineage OS, even that it suppose to be stock rom.
I try below method to restore stock rom: https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
With this firmware: https://firmware.center/firmware/Motorola/Moto X Style/Stock/XT1572/ and android 7.0 But I constantly have error msg: "(bootloader) Preflash validation failed FAILED (remote failure)"
I tried to look for solutions but at this point it starts to getting quite too difficult to grasp what should I try next, I do not want to brick the phone for good.
Could you please give me any advice and suggestions? I have Lineage OS on three other devices, never had this type of issues before.
which firmware you were on when you unlocked bootloader and flashed Lineage? Marshmallow or Nougat?
antariksh said:
which firmware you were on when you unlocked bootloader and flashed Lineage? Marshmallow or Nougat?
Click to expand...
Click to collapse
Nougat, 7.0 for sure, with October security patch I think.
zonewelld said:
Nougat, 7.0 for sure, with October security patch I think.
Click to expand...
Click to collapse
Flash this TWRP: https://forum.xda-developers.com/showpost.php?p=74235571&postcount=917
Flash this LineageOS: https://forum.xda-developers.com/showpost.php?p=74980159&postcount=1054
It's a pretty stable build, you might able to get it to boot up.
antariksh said:
Flash this TWRP: https://forum.xda-developers.com/showpost.php?p=74235571&postcount=917
Flash this LineageOS: https://forum.xda-developers.com/showpost.php?p=74980159&postcount=1054
It's a pretty stable build, you might able to get it to boot up.
Click to expand...
Click to collapse
Holly! It boots! Thanks a lot!
I tried a lot of ROMs, but all on 3.2.1 TWRP, maybe that was the problem. Anyway it seems to be fine now, I am very grateful for your help with it.
All the best!
zonewelld said:
Holly! It boots! Thanks a lot!
I tried a lot of ROMs, but all on 3.2.1 TWRP, maybe that was the problem. Anyway it seems to be fine now, I am very grateful for your help with it.
All the best!
Click to expand...
Click to collapse
It wasn't only the TWRP issue. From Marshmallow to Nougat was a major update for our device. Once upgraded to Nougat the data partition format is F2FS am not sure, but hope you get my point.
Developers had to compile ROMs based on this new updated Kernel, Modem and Vendor.
I have been using this unofficial builds for a week now and they are stable. No major bugs.
You can also flash the official Nougat firmware image over fastboot, in case you you wanna go back to Stock.
In case you want to try this old ROMs, you have to flash Marshmallow modem and then it will boot.
antariksh said:
From Marshmallow to Nougat was a major update for our device. Once upgraded to Nougat the data partition format is F2FS am not sure, but hope you get my point.
Developers had to compile ROMs based on this new updated Kernel, Modem and Vendor.
I have been using this unofficial builds for a week now and they are stable. No major bugs.
You can also flash the official Nougat firmware image over fastboot, in case you you wanna go back to Stock.
Click to expand...
Click to collapse
Thanks, I will keep that in mind, but I think I am good for now, had enough of messing with this phone for next couple of weeks
Cheers!
zonewelld said:
Thanks, I will keep that in mind, but I think I am good for now, had enough of messing with this phone for next couple of weeks
Cheers!
Click to expand...
Click to collapse
hahahahaha fair enough. I just compiled Nuclea ROM based on LineageOS for Nougat Kernel and Modem. Feel free to try it next week. Uploading....
antariksh said:
hahahahaha fair enough. I just compiled Nuclea ROM based on LineageOS for Nougat Kernel and Modem. Feel free to try it next week. Uploading....
Click to expand...
Click to collapse
You're evil! I... must... resist... temptation....
Thanks for all your hard work for the community!
Hello again all!
So I've recently discovered the glory of GSI / Treble roms! Good stuff! But after much banter with Ressurection remix's 9.0 GSI rom, I have still yet to get it working, and wasn't sure if I'm just missing something.
So far, what I've tried is:
- Wiping everything (caches, system, data) as well as formatting my data partition
- then installing the rom. after a couple of routine-looking reboots, the system boots without gapps functioning great.
- quick settings states 'No SIM card', which is false
- reinstalled rom countless times
- restored to functioning rom, backed up EFS, reinstalled RRemix in the same fashion, restored EFS backup. No solve there.
And with that, I'm out of ideas and without much knowledge of GSI / Treble processes, I'm not even sure how to word searches for help. Any advice ya'll?
Hey man, let me know if you still haven’t gotten this resolved and are still looking to do so. After days of research and experimentation I finally created a process to reliably flash a fully functional RR 7.X rom. I can provide my boot.img and instructions if you need them.
Derbyy said:
Hey man, let me know if you still haven’t gotten this resolved and are still looking to do so. After days of research and experimentation I finally created a process to reliably flash a fully functional RR 7.X rom. I can provide my boot.img and instructions if you need them.
Click to expand...
Click to collapse
I'm interested in this for sure. I'm curious, are you guys using the A only IMG of treble ROMs?
jal3223 said:
I'm interested in this for sure. I'm curious, are you guys using the A only IMG of treble ROMs?
Click to expand...
Click to collapse
It’s funny you should reply to me on today of all days. This morning, after a month of testing, I finally succeeded in getting my RP2 to A/B boot RR 7, TWRP, AND have it rooted with Magisk. I couldn’t believe I finally got it. AMA
Are any of you on Verizon? I've tried multiple GSIs and have never gotten LTE to work properly.
Reznor7 said:
Are any of you on Verizon? I've tried multiple GSIs and have never gotten LTE to work properly.
Click to expand...
Click to collapse
Did you try an A only image? It should work as it doesn't touch the vendor image or CSC. At first I was trying AB images on my Note 9 and could never get signal. I found out that we are only supposed to use the A only images on that device and my problems were solved. I haven't tried anything on my Razer Phone 2 though as the stock ROM is pretty much exactly what I want. It's worth a try.
Need RR help.
Derbyy said:
Hey man, let me know if you still haven’t gotten this resolved and are still looking to do so. After days of research and experimentation I finally created a process to reliably flash a fully functional RR 7.X rom. I can provide my boot.img and instructions if you need them.
Click to expand...
Click to collapse
Hey, can I get that boot.img and instructions if you can still provide them? I want to install r.r 7.x please. Sorry for messaging you 4 months later.
jal3223 said:
Did you try an A only image? It should work as it doesn't touch the vendor image or CSC. At first I was trying AB images on my Note 9 and could never get signal. I found out that we are only supposed to use the A only images on that device and my problems were solved. I haven't tried anything on my Razer Phone 2 though as the stock ROM is pretty much exactly what I want. It's worth a try.
Click to expand...
Click to collapse
sorry to disturb you years later,but why not try to flash another gsi like crdroid,boot into it and flash you rr rom back?
this strange method worked on my redmi 10a