Related
Hi I get an Error 7 when I wanna installeren an rom. AICP.
Phone is rooted. Op3.
Help
Error 7? Sounds like an old TWRP version...
Which version of TWRP? if it's not the latest, update it and try flashing again. It's a common problem
therightperson_630 said:
Error 7? Sounds like an old TWRP version...
Which version of TWRP? if it's not the latest, update it and try flashing again. It's a common problem
Click to expand...
Click to collapse
I Have the
3.0.2.1 Version
https://dl.twrp.me/oneplus3/
Looks like you're not the only one with that problem. Try flashing an older version of AICP and upgrading/dirty flashing to the newer version, see if that works.
What rom are you coming from? Oxygen OS?
therightperson_630 said:
Looks like you're not the only one with that problem. Try flashing an older version of AICP and upgrading/dirty flashing to the newer version, see if that works.
What rom are you coming from? Oxygen OS?
Click to expand...
Click to collapse
Hi, I tried that.
Unforneltly not working.
Yes, Oxygen OS, did also an older Oxygen, but nothing helps.
YourTheBest said:
Hi, I tried that.
Unforneltly not working.
Yes, Oxygen OS, did also an older Oxygen, but nothing helps.
Click to expand...
Click to collapse
Right I see, if I'm not wrong, you can't just install CM13 or Nougat from Oxygen OS directly.. you'll have to flash the latest CM13 nightly to get the right firmware:
http://get.cm/?device=oneplus3
once you're on CM13, wipe your device and install that AICP Nougat rom.
Should work. I had the same problem switching between Oxygen OS and CM
Tell me how it goes
therightperson_630 said:
Looks like you're not the only one with that problem. Try flashing an older version of AICP and upgrading/dirty flashing to the newer version, see if that works.
What rom are you coming from? Oxygen OS?
Click to expand...
Click to collapse
therightperson_630 said:
Right I see, if I'm not wrong, you can't just install CM13 or Nougat from Oxygen OS directly.. you'll have to flash the latest CM13 nightly to get the right firmware:
http://get.cm/?device=oneplus3
once you're on CM13, wipe your device and install that AICP Nougat rom.
Should work. I had the same problem switching between Oxygen OS and CM
Tell me how it goes
Click to expand...
Click to collapse
I really gonna love you if that's gonna work!
Give me 15 minutes!
therightperson_630 said:
Right I see, if I'm not wrong, you can't just install CM13 or Nougat from Oxygen OS directly.. you'll have to flash the latest CM13 nightly to get the right firmware:
http://get.cm/?device=oneplus3
once you're on CM13, wipe your device and install that AICP Nougat rom.
Should work. I had the same problem switching between Oxygen OS and CM
Tell me how it goes
Click to expand...
Click to collapse
Same story, latest CM 13.0 nightly ROM.
I ran into this error when trying to flash custom kernels. I found that my /system partition was messed up. It would not mount in TWRP and the size reported was wrong in TWRP and OOS. I restored just the /system partition from a recent nandroid in TWRP and it resolved the issue. I don't know if it applies to this but maybe points you in the right direction.
YourTheBest said:
Same story, latest CM 13.0 nightly ROM.
Click to expand...
Click to collapse
Try flashing the latest CM14 unofficial now? like this one
https://www.androidfilehost.com/?w=files&flid=106864
It could be a problem with their latest rom too
therightperson_630 said:
Right I see, if I'm not wrong, you can't just install CM13 or Nougat from Oxygen OS directly.. you'll have to flash the latest CM13 nightly to get the right firmware:
http://get.cm/?device=oneplus3
once you're on CM13, wipe your device and install that AICP Nougat rom.
Should work. I had the same problem switching between Oxygen OS and CM
Tell me how it goes
Click to expand...
Click to collapse
therightperson_630 said:
Try flashing the latest CM14 unofficial now? like this one
https://www.androidfilehost.com/?w=files&flid=106864
It could be a problem with their latest rom too
Click to expand...
Click to collapse
Still the same issue.
YourTheBest said:
Still the same issue.
Click to expand...
Click to collapse
So you've never had any problems with CM13 roms but Nougat roms always give you error 7?
Do you do a full wipe every time?
therightperson_630 said:
So you've never had any problems with CM13 roms but Nougat roms always give you error 7?
Do you do a full wipe every time?
Click to expand...
Click to collapse
I had never CM13.
I tried to install that over the original oxygen OS
therightperson_630 said:
Looks like you're not the only one with that problem. Try flashing an older version of AICP and upgrading/dirty flashing to the newer version, see if that works.
What rom are you coming from? Oxygen OS?
Click to expand...
Click to collapse
Oke, got it working.
I did an soft/hard brickt.
CLEAN EVERYTHING.
And now is AICP running.
Only I now get an error 4 with installing gapps.
Pff, f*ck my life.
Thanks for helping my friend. I gonna take an nap now for 2 hours.
You are amazing! J'taime mon amour!<3
YourTheBest said:
I had never CM13.
I tried to install that over the original oxygen OS
Click to expand...
Click to collapse
You say you tried to install over OOS? Without wiping first? You should do a full wipe when switching ROMs.
Hello guys, i have a anyonning problem.
I have install the ViperOS in my xiaomi mi5s and open gapps with no problem. It's running very well.
But, i can't watch no one video, have freezes all time and no sound. This is happening in all apks, YouTube, instagram, and others.
Someone have the solution for solve this? I don't want back to the MIUI never more :crying:
Regards
Edit: i have already try to install lineageOS too, but the problem is the same. And another OG version too, no sucess
Flash the latest firmware
How can i update my firmware?
Edit: i already have the latest version of the ROM. I need another update to install?
https://github.com/fjtrujy/capricornCNFirmware
Download latest firmware from there and just flash it via twrp. It should solve the problem
And what was the solution? I have the same problem
Flash 7.12.21 because Viper OS is old ROM and it won't probablu work with newer firmwares. But yuo can always try
predragiPredrag said:
Flash 7.12.21 because Viper OS is old ROM and it won't probablu work with newer firmwares. But yuo can always try
Click to expand...
Click to collapse
Thank you
Hello,
I'm considering going back to the stock ROM in my moto z play XT1635-02 retla1st but I would like to know if I would have a problem installing the RETAIL version when receiving OTA's or some other problem.
I currently have the bootloader unlocked and a compilation that is not the official one but I want to remove the root and receive the updates without any inconvenience.
best regards
_heberlopez95 said:
Hello,
I'm considering going back to the stock ROM in my moto z play XT1635-02 retla1st but I would like to know if I would have a problem installing the RETAIL version when receiving OTA's or some other problem.
I currently have the bootloader unlocked and a compilation that is not the official one but I want to remove the root and receive the updates without any inconvenience.
best regards
Click to expand...
Click to collapse
I do not know if you can downgrade from a 7.1 ROM to a 6.x Stock via RSD and have your phone usable. With some phones if you downgrade to MM you brick it.
If it survives, you would then need to find a way to lock the bootloader.
In the same Android versión it's possible install a retail ROM?
_heberlopez95 said:
In the same Android versión it's possible install a retail ROM?
Click to expand...
Click to collapse
I believe if your phone (bootloaders) is 7.x you can RSD 7.x and if phone is 6.x you can RSD 6.x .
KrisM22 said:
I believe if your phone (bootloaders) is 7.x you can RSD 7.x and if phone is 6.x you can RSD 6.x .
Click to expand...
Click to collapse
I understand but my question is, I have a ROM retla1st 7.1.1 and my bootloader unlocked I want to close the bootloader and flash the stock ROM but I can not find the version of retla1st with 7.1.1 only encounter 6.0.1 and I can not go back to MM because I understand that the phone is damaged for which I want to install the stock 7.1.1 retail ROM will there be any problems?
I understand but my question is, I have a ROM retla1st 7.1.1 and my bootloader unlocked I want to close the bootloader and flash the stock ROM but I can not find the version of retla1st with 7.1.1 only encounter 6.0.1 and I can not go back to MM because I understand that the phone is damaged for which I want to install the stock 7.1.1 retail ROM will there be any problems?
_heberlopez95 said:
I understand but my question is, I have a ROM retla1st 7.1.1 and my bootloader unlocked I want to close the bootloader and flash the stock ROM but I can not find the version of retla1st with 7.1.1 only encounter 6.0.1 and I can not go back to MM because I understand that the phone is damaged for which I want to install the stock 7.1.1 retail ROM will there be any problems?
Click to expand...
Click to collapse
yeah - I don't know - You could try the links at this post and see if it answers your needs...: Let me know!
https://forum.xda-developers.com/showpost.php?p=75364150&postcount=7
KrisM22 said:
yeah - I don't know - You could try the links at this post and see if it answers your needs...: Let me know!
https://forum.xda-developers.com/showpost.php?p=75364150&postcount=7
Click to expand...
Click to collapse
I used this guide today, it worked without any problems. I went from rooted 7.1.1 stock september security patch to 7.1.1 stock november security patch with locked bootloader. OTA december security patch worked as well. I even unlocked the bootloader again and am now rooted with magisk safety net passing
tschannik26 said:
I used this guide today, it worked without any problems. I went from rooted 7.1.1 stock september security patch to 7.1.1 stock november security patch with locked bootloader. OTA december security patch worked as well. I even unlocked the bootloader again and am now rooted with magisk safety net passing
Click to expand...
Click to collapse
Thanks! I also appreciate knowing what you were on and what it gave you! No problems with carrier or modems? Great!!! @SupahCookie may have a super fix-all! Hope you gave tons of thanks there
KrisM22 said:
Thanks! I also appreciate knowing what you were on and what it gave you! No problems with carrier or modems? Great!!! @SupahCookie may have a super fix-all! Hope you gave tons of thanks there
Click to expand...
Click to collapse
No problems whatsoever. I'm on t-mobile germany, channel was reteu before and after
tschannik26 said:
No problems whatsoever. I'm on t-mobile germany, channel was reteu before and after
Click to expand...
Click to collapse
Great!!!!!
thanks a lot for your help guys ..!
KrisM22 said:
Thanks! I also appreciate knowing what you were on and what it gave you! No problems with carrier or modems? Great!!! @SupahCookie may have a super fix-all! Hope you gave tons of thanks there
Click to expand...
Click to collapse
Super fix, sounds amazing :3
SupahCookie said:
Super fix, sounds amazing :3
Click to expand...
Click to collapse
incroyable!!!
Greetings developers, someone of you can help me with the following problem, I can not install the rom AOSP the TWRP does not mark me any problem simply installs but when starting it restarts constantly without going through the restart, like the rom AOEX rom Validus, however I can install the rom Xperience, DotOs, RRemix and the Stock without any problem, you know why that happens, my device is a Moto Z Play XT1635-02.
You should use treble twrp to install rom
JR Bautista said:
You should use treble twrp to install rom
Click to expand...
Click to collapse
If I am using a TWRP of treble, however as i say that if installing an AOSP ROM with Android 9 or 8.1 does not pass from the logo and restarts, but if you install the Rom Xperience. 8.1 If run without problems, but the same Rom Xperience. 13 (Android P) does not run, I have tried with the DPI images and do not correrily
MirandaEduardo said:
If I am using a TWRP of treble, however as i say that if installing an AOSP ROM with Android 9 or 8.1 does not pass from the logo and restarts, but if you install the Rom Xperience. 8.1 If run without problems, but the same Rom Xperience. 13 (Android P) does not run, I have tried with the DPI images and do not correrily
Click to expand...
Click to collapse
update your bootloader to oreo?
JR Bautista said:
update your bootloader to oreo?
Click to expand...
Click to collapse
Yes, 0xC182
MirandaEduardo said:
If I am using a TWRP of treble, however as i say that if installing an AOSP ROM with Android 9 or 8.1 does not pass from the logo and restarts, but if you install the Rom Xperience. 8.1 If run without problems, but the same Rom Xperience. 13 (Android P) does not run, I have tried with the DPI images and do not correrily
Click to expand...
Click to collapse
do a backup of your files (if you are installing xpe you need a Treble supported TWRP) in xpe 13 maybe you need to do a format data (idk why but some users have a weird bug and only can be fixed if you do a format data
so do a format data from TWRP wipe-->format data-> write yes do a swipe reboot to recovery
copy all your files the rom , install it and enjoy!
if you are installing AOSP you should use twrp from alberto
TeamMex said:
do a backup of your files (if you are installing xpe you need a Treble supported TWRP) in xpe 13 maybe you need to do a format data (idk why but some users have a weird bug and only can be fixed if you do a format data
so do a format data from TWRP wipe-->format data-> write yes do a swipe reboot to recovery
copy all your files the rom , install it and enjoy!
if you are installing AOSP you should use twrp from alberto
Click to expand...
Click to collapse
Ok, thanks, friend, I'm going to try it like that
MirandaEduardo said:
Greetings developers, someone of you can help me with the following problem, I can not install the rom AOSP the TWRP does not mark me any problem simply installs but when starting it restarts constantly without going through the restart, like the rom AOEX rom Validus, however I can install the rom Xperience, DotOs, RRemix and the Stock without any problem, you know why that happens, my device is a Moto Z Play XT1635-02.
Click to expand...
Click to collapse
Hello brother i think you have a stock rom for xt 1635 02 addison single sim. Bro can you upload it for me or some kind of link? Appreciate your kind help
khanpatriot said:
Hello brother i think you have a stock rom for xt 1635 02 addison single sim. Bro can you upload it for me or some kind of link? Appreciate your kind help
Click to expand...
Click to collapse
Yes, this Is a link
https://drive.google.com/file/d/1W-DXW1qm0g6GaALjKuA1pvM-_RHqlZ4j/view
Thanks alot
Oooppss one more query does software channel matter? I'm currently running lineage os 14.1 and i can't find the exact software channel of my device I'm little confused is it retus retail or some other channel. Can u plz help?
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
EDIT:
I solved the problem with the kind help from phhusson and the guidance from Lanreallenjay (thanks, both of you!), so I'm trying to provide the solution for anyone that might be having the same problem as I had. So here it is:
For PIE GSI: use stock kernel/vendor (anything stock), flash the GSI, then flash Magisk -> it should boot fine now (only tested with phhusson's GSI. I had vibrating restart loops before, I wasn't installing magisk, that was my mistake)
For Android 10 GSI: same as above, but install the modded Magisk from phhusson's git (located @ v200 android 10 gsi post) instead of the normal one .
itShouldWork said:
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
Click to expand...
Click to collapse
What's your phone's specifications?
Lanreallenjay said:
What's your phone's specifications?
Click to expand...
Click to collapse
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
itShouldWork said:
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
Click to expand...
Click to collapse
Ask for help here
https://t.me/phhtreble/283195 <---
Read before any question ^^^
After flashing G960FXXS7CSJ3 November stock firmware I can no longer flash anything.
(can't mount data partition)
When I try downgrading to G960FXXU5CSF2 June firmware Odin fails and the screen says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 7 BINARY: 5
November G960FXXS7CSJ3 seems to have upgraded the bootloader security, does anyone know a fix?
itShouldWork said:
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
EDIT:
I solved the problem with the kind help from phhusson and the guidance from Lanreallenjay (thanks, both of you!), so I'm trying to provide the solution for anyone that might be having the same problem as I had. So here it is:
For PIE GSI: use stock kernel/vendor (anything stock), flash the GSI, then flash Magisk -> it should boot fine now (only tested with phhusson's GSI. I had vibrating restart loops before, I wasn't installing magisk, that was my mistake)
For Android 10 GSI: same as above, but install the modded Magisk from phhusson's git (located @ v200 android 10 gsi post) instead of the normal one .
Click to expand...
Click to collapse
So from stock you flashed AOSP 10 GSI to system partition then phh's magisk (in TWRP) then it works for you?
rupert3k said:
So from stock you flashed AOSP 10 GSI to system partition then phh's magisk (in TWRP) then it works for you?
Click to expand...
Click to collapse
Yep, it does. Buuut the rom is not stable at all, I've got random reboots/ crashes when opening settings and such, not usable at all. I'm on ONE UI 2.0 beta now which is much more stable (daily driver stable actually).
rupert3k said:
After flashing G960FXXS7CSJ3 November stock firmware I can no longer flash anything.
(can't mount data partition)
When I try downgrading to G960FXXU5CSF2 June firmware Odin fails and the screen says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 7 BINARY: 5
November G960FXXS7CSJ3 seems to have upgraded the bootloader security, does anyone know a fix?
Click to expand...
Click to collapse
Have you tried formatting data with TWRP (to the part when it asks you to write "yes") then flash no-verity?
You should at least be able to flash TWRP. If you can't, just download the proper USB drivers for your device, it might be the culprit.
Cheers!
itShouldWork said:
Yep, it does. Buuut the rom is not stable at all, I've got random reboots/ crashes when opening settings and such, not usable at all. I'm on ONE UI 2.0 beta now which is much more stable (daily driver stable actually).
Click to expand...
Click to collapse
Phh just hinted it's likely Pie vendor causing panics:
"First you need to flash stock rom. Then install magisk and then this gsi.
Though please note that on Pie vendor, S9 kernel panics and reboot every few minutes, so it is highly unusable."
itShouldWork said:
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
Click to expand...
Click to collapse
I have tried Android 10 GSI , using latest Q update
ZoiraP said:
I have tried Android 10 GSI , using latest Q update
Click to expand...
Click to collapse
Is it usable? any random reboots/ annoying instability?
itShouldWork said:
Is it usable? any random reboots/ annoying instability?
Click to expand...
Click to collapse
I have tried it partly , nfc isnt working , camera quality is bad , Bluetooth working , audio working , magisk working . I'll use it a bit more and tell you.
ZoiraP said:
I have tried it partly , nfc isnt working , camera quality is bad , Bluetooth working , audio working , magisk working . I'll use it a bit more and tell you.
Click to expand...
Click to collapse
Camera quality might be fixed with Google cam, if you find a good port.
Not to derail the thread but I just noticed after installing Android 10 beta 2 Treble Info now reports my S9 supports Treble A/B, curious no?
rupert3k said:
Not to derail the thread but I just noticed after installing Android 10 beta 2 Treble Info now reports my S9 supports Treble A/B, curious no?
Click to expand...
Click to collapse
Wait what? That's interesting...
Can someone with more experience enlighten us about the differences between the A only and A/B?
A\B
itShouldWork said:
Wait what? That's interesting...
Can someone with more experience enlighten us about the differences between the A only and A/B?
Click to expand...
Click to collapse
No real experience but A\B devices have two slots ie double the partitions (OnePlus has 67) .
This allows updates to be installed while running from slot A while the updated system is copied to B.
Apparently Q requires A\B so now we're on Q may as well try that next time we're curious
Phh just released:
AOSP 10.0 v208
Fix suspend/dt2w for Samsung Q vendor
Fix backlight for Samsung Q vendor
Samsung Q's fine, love gestures but the bloat is killing me.
You can tell Q's going to be so much leaner without bixby & friends.
Glad we installed it to get compatible but I think now we probably stand a better chance with 10 GSI's, hopefully LOS17 & Pixel Experience get updated again soon.
Wondering whether to following the rooting instructions yet?
Phh did say "flash stock rom then magisk and then gsi"
https://forum.xda-developers.com/galaxy-s9/how-to/one-ui-2-beta-rooting-installing-twrp-t4012961
ZoiraP's wondering why we sooo slow lol!
Wow this looks good: https://forum.xda-developers.com/ga...-s9--s9-cross-device-development/rom-t4020939