Here are the download links and the tutorial on how to flash:
Pixel C: http://www.jide.com/remixos/devices/pixelc
Nexus 9: http://www.jide.com/remixos/devices/nexus9
Tutorial on how to flash onto your device:
https://jide.zendesk.com/knowledge/a...rand_id=449827
Thanks!
This is actually a really good update. Question though. Will we ever be able to use our own launcher? And what happened to the old choice of not having all icons on home screen?
RemixOS_Jason said:
Here are the download links and the tutorial on how to flash:
Pixel C: http://www.jide.com/remixos/devices/pixelc
Nexus 9: http://www.jide.com/remixos/devices/nexus9
Tutorial on how to flash onto your device:
https://jide.zendesk.com/knowledge/a...rand_id=449827
Thanks!
Click to expand...
Click to collapse
How to flash via TWRP??
Sent from my SM-G935F using Tapatalk
sheenswizner said:
How to flash via TWRP??
Click to expand...
Click to collapse
You don't. You use adb/fastboot, and give it a go that way. A little bit more work, but not that big a deal.
So I suppose if we want to come from a nexus 9 android n preview, we have to flash the factory image from the last 6.0.1 before we flash the remix os?
looks nice but does not support LTE, says to insert sim card even though it is already there
blop135 said:
So I suppose if we want to come from a nexus 9 android n preview, we have to flash the factory image from the last 6.0.1 before we flash the remix os?
Click to expand...
Click to collapse
If you have TWRP installed, it's easy.
1. Reboot into recovery
2. Wipe data, cache, system, dalvik
3. Reboot bootloader
4. Fastboot flash the provided (remixOS) bootloader and vendor
5. Flash the rest of the files, but not recovery (unless you don't want twrp)
6. Select HBoot, then select recovery.
7. (Optional) If you are unencrypted, and want to remain so, flash fed patch v8 in recovery. Now reboot
Doing it this way, you don't lose any files on your device, and your device remains unencrypted plus with twrp. If you want to go back to a regular ROM, all you'll have to do is do your wipes in twrp, flash the correct bootloader and vendor, and you're set. It's a lot easier than transferring stuff on and off every time.
dictionary said:
If you have TWRP installed, it's easy.
1. Reboot into recovery
2. Wipe data, cache, system, dalvik
3. Reboot bootloader
4. Fastboot flash the provided bootloader
5. Flash the rest of the files, but not recovery (unless you don't want twrp)
6. Select HBoot, then select recovery.
7. (Optional) If you are unencrypted, and want to remain so, flash fed patch v8 in recovery. Now reboot
Doing it this way, you don't lose any files on your device, and your device remains unencrypted plus with twrp. If you want to go back to a regular ROM, all you'll have to do is do your wipes in twrp, flash the correct bootloader and vendor, and you're set. It's a lot easier than transferring stuff on and off every time.
Click to expand...
Click to collapse
I don't have TWRP^^ , I flashed Remix OS 2.0 with adb
blop135 said:
I don't have TWRP^^ , I flashed Remix OS 2.0 with adb
Click to expand...
Click to collapse
**fastboot
Okay that works too. I just like keeping twrp instead of stock recovery. You don't have to completely flash back to stock though. Only thing you'll need are bootloader and vendor provided.
dictionary said:
**fastboot
Okay that works too. I just like keeping twrp instead of stock recovery. You don't have to completely flash back to stock though. Only thing you'll need are bootloader and vendor provided.
Click to expand...
Click to collapse
Ok thank you, I'll try to flash the last version and will see
hjlow said:
looks nice but does not support LTE, says to insert sim card even though it is already there
Click to expand...
Click to collapse
Me too, please help~
dictionary said:
**fastboot
Okay that works too. I just like keeping twrp instead of stock recovery. You don't have to completely flash back to stock though. Only thing you'll need are bootloader and vendor provided.
Click to expand...
Click to collapse
OK so after some research, I don't find the correct stock bootloader for this ROM, any ideas?
blop135 said:
OK so after some research, I don't find the correct stock bootloader for this ROM, any ideas?
Click to expand...
Click to collapse
https://www.dropbox.com/s/beyoodfca46z83r/bootloader-flounder-3.48.0.0135.img?dl=0
if you do a search for nexus img you can download it directly from google...just unzip it...and tbh it looks as though it's the same bootloader but i'd flash it just to be safe
my opinion, for whatever it's worth, it's not too bad....i do kinda enjoy opening apps in little pop up windows that i can minimize/close/expand....biggest frustration so far - i like to read on here a lot, vertically it's fine, landscape gives a big white bar on the side and you cannot view the full page you're on, even playing around with the dpi
damngood98 said:
https://www.dropbox.com/s/beyoodfca46z83r/bootloader-flounder-3.48.0.0135.img?dl=0
if you do a search for nexus img you can download it directly from google...just unzip it...and tbh it looks as though it's the same bootloader but i'd flash it just to be safe
my opinion, for whatever it's worth, it's not too bad....i do kinda enjoy opening apps in little pop up windows that i can minimize/close/expand....biggest frustration so far - i like to read on here a lot, vertically it's fine, landscape gives a big white bar on the side and you cannot view the full page you're on, even playing around with the dpi
Click to expand...
Click to collapse
Yes I was looking from Google directly, do you think the last 6.0.1 will be good?
Remix OS 2.0 is nice already but on the nexus 9 but little bit small for display, waiting for the nexus 9 keyboard from Google that I ordered, hope it will work like a charm.
blop135 said:
Yes I was looking from Google directly, do you think the last 6.0.1 will be good?
Remix OS 2.0 is nice already but on the nexus 9 but little bit small for display, waiting for the nexus 9 keyboard from Google that I ordered, hope it will work like a charm.
Click to expand...
Click to collapse
yes, i would use the last one, whether you're going to stock or just to flash another rom
blop135 said:
OK so after some research, I don't find the correct stock bootloader for this ROM, any ideas?
Click to expand...
Click to collapse
For what ROM? The RemixOS rom comes with the correct bootloader to flash
Yep I just saw it, I was not sure, thank you
Pleasantly surprised with the update. Feels smooth so far and very glad that we can add widgets to the desktop .
The split keyboard function also makes the keyboard usable while holding the tablet in landscape mode.
There's a easiest way to flash this remix 3.0 ROM on nexus 9 rather than using the fastboot or adb, I can confirm flashing via FlashFire app works by clicking on 'Firmware' then find the .tgz file you downloaded for the remix 3.0. The ROM I had before was completely different as well, slim9 so I was quite rather impressed it still worked without any problems, boot loops but make sure u do the usual wipe cache, system, data etc before flashing. (Don't need to wipe internal storage either)
Its a clean, smooth, fast responsive ROM, huge update from Remix 2.0. Thanks Remix devs <3
Sent from my SM-A300FU using XDA-Developers mobile app
MpandAUS said:
There's a easiest way to flash this remix 3.0 ROM on nexus 9 rather than using the fastboot or adb, I can confirm flashing via FlashFire app works by clicking on 'Firmware' then find the .tgz file you downloaded for the remix 3.0. The ROM I had before was completely different as well, slim9 so I was quite rather impressed it still worked without any problems, boot loops but make sure u do the usual wipe cache, system, data etc before flashing. (Don't need to wipe internal storage either)
Its a clean, smooth, fast responsive ROM, huge update from Remix 2.0. Thanks Remix devs <3
Sent from my SM-A300FU using XDA-Developers mobile app
Click to expand...
Click to collapse
Couldn't agree more =)
Related
So I flashed the 7.1.1 update and everything was fine. I then tried to root through TWRP with the most recent version of recovery and and SuperSu and when I went to reboot it would get to the "Google" splash screen and go back to the warning. I then tried to restore to my Nandroid that I made right before the 7.1.1 flash but it does the same thing. I ended up doing a factory reset, still looping. I tried flashing an old firmware but it still would loop. I got desperate and did a full wipe and then flashed the old firmware from September's update but it still will not boot. I'm a long time lurker I just don't post much. Any help will be appreciated. Thanks in advance!
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Ahh, great. I tried searching to see if anyone else posted anything, couldn't find it.
jamaniek said:
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page32
Welcome to the club
Click to expand...
Click to collapse
Wait are you able to get into Recovery?
ChazLanier said:
Wait are you able to get into Recovery?
Click to expand...
Click to collapse
Nope. And so are other folks.
But if you can, there's still hope to save your device.
What version of twrp were you using?? Also what company makes the storage (not memory) on your device?
jamaniek said:
Nope. And so are other folks.
But if you can, there's still hope to save your device.
Click to expand...
Click to collapse
I can still get into recovery. I just can't get it past the Google splash screen.
ChazLanier said:
I can still get into recovery. I just can't get it past the Google splash screen.
Click to expand...
Click to collapse
Have you tried installing custom ROM, instead of a stock one?
And tell us what @ArminasAnarion asked for. There may be a pattern here. :good:
I haven't tried a custom ROM. I'll try that if I get any down time at work. Also, I'll check for you @ArminasAnarion in a bit.
Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?
ChazLanier said:
Might be a noob question, but how do I get the custom rom files over to my phone to flash in recovery?
Click to expand...
Click to collapse
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!
ArminasAnarion said:
Well if you cant access twrp then your not flashing anything; did you try downloading the latest Nexus 6p factory image and using adb to flash it?? If you need help with that I can lay it out for you. Also there was an efs partition issue with twrp 3.0.2-1 and down so make sure your twrp is 3.0.2-2!
Click to expand...
Click to collapse
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.
ChazLanier said:
I can access TWRP. I haven't tried the latest factory image, only September's release. I just tried a custom rom and it gets to the Google screen but then loops just after the G starts to animate.
Click to expand...
Click to collapse
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.
ArminasAnarion said:
Make sure your using twrp 3.0.2-2; and download the latest factory image for the Nexus 6p (NBD90X) and use adb (fastboot) to flash that whole thing. Extract the files to your android sdk platform tools folder then run the flash-all.bat file. (If you are using a 64gb or 128gb device DONT DO THIS) Only do this with the 32gb model. If its a 64 or 128 model go here -> http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and go to sub section 10. How To Flash The Factory Images (And Return To Stock) (On post two) and follow that.
Click to expand...
Click to collapse
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.
ChazLanier said:
Downloading the image now. I'm familiar on how to flash stock images, they're how I usually do all of my updates.
Click to expand...
Click to collapse
Oh okay cool! Good luck!
ArminasAnarion said:
What version of twrp were you using?? Also what company makes the storage (not memory) on your device?
Click to expand...
Click to collapse
Samsung storage, and I thought I was on -2 but it seems like I was on -1.
ArminasAnarion said:
Oh okay cool! Good luck!
Click to expand...
Click to collapse
Newest image didn't work either..
Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.
FWIW, I successfully updated to 7.1.1 NPF10C and rooted by using fastboot to flash bootloader, radio, boot, system, and vendor. Then used TWRP 3.0.2-2 to flash SuperSU 2.78 SR1. No issues.
Howie Dub said:
Have you tried WugFresh's Nexus Root Toolkit? Not sure if it will work for your situation, but it has an option to restore to factory settings and unroot if you're soft-bricked or bootlooped. Might be worth a shot if everything else isn't working.
Click to expand...
Click to collapse
No luck on this either.
Hi,
I just unlocked the bootloader of my Moto G Plus 4 via adb, and after that I switched it on, it worked fine and I transferred SuperUser.zip into my phone's internal memory, and then tried to flash it through recovery, (following the sleps I read somewhere), since then my phone is not rebooting - it is rebooting into bootloader and I can enter recovery as well, but Im not able to reboot my phone. The device is being detected via adb when it is in recovery mode, but not in bootloader. Is this issue fixable? Please help me fix this.
EDIT: I forgot to mention, I'm not getting the boot animation as well. I press the power key and nothing at all happens.
d1nesh said:
Hi,
I just unlocked the bootloader of my Moto G Plus 4 via adb, and after that I switched it on, it worked fine and I transferred SuperUser.zip into my phone's internal memory, and then tried to flash it through recovery, (following the sleps I read somewhere), since then my phone is not rebooting - it is rebooting into bootloader and I can enter recovery as well, but Im not able to reboot my phone. The device is being detected via adb when it is in recovery mode, but not in bootloader. Is this issue fixable? Please help me fix this.
Click to expand...
Click to collapse
You got into bootloop, just download the stock ROM and then flash it again, follow any guide over XDA or see YouTube for more help. Flash ROM without locking bootloader will be good.
Sent from my Moto G4 Plus using Tapatalk
avirk said:
You got into bootloop, just download the stock ROM and then flash it again, follow any guide over XDA or see YouTube for more help. Flash ROM without locking bootloader will be good.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I forgot to mention, I'm not getting the bootanimation as well, I press the power button and nothing at all happens.
d1nesh said:
I forgot to mention, I'm not getting the bootanimation as well, I press the power button and nothing at all happens.
Click to expand...
Click to collapse
Yes that is what happen after unlocking Boot loader, just flash the stock ROM using any tutorial over XDA without locking the boot loader and then follow the proper instructions to root your mobile. Rooting is very easy on Android N. So I will say flash android N and then proceed.
Sent from my Moto G4 Plus using Tapatalk
avirk said:
Yes that is what happen after unlocking Boot loader, just flash the stock ROM using any tutorial over XDA without locking the boot loader and then follow the proper instructions to root your mobile. Rooting is very easy on Android N. So I will say flash android N and then proceed.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
First thing, your query doesn't belong to the development thread. It should had been created in "Questions and Answers"
Second thing, if you flash supersu on stock rom it won't boot due some security measures of Moto. Instead flash ElementalX kernel first and then flash supersu.
d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
All information that you will need can be found here. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
For the latest stock nougat firmware for XT1643 check this link https://mega.nz/#!ystC2ZSL!ql6cyC5v5RgLQfo7G44mhi7Ng-AQBvtsouKxKinbHi8
If you have some confusion about flashing, be sure to check it out before going on. I believe you have some knowledge about fastboot and using it.
==vj== said:
First thing, your query doesn't belong to the development thread. It should had been created in "Questions and Answers"
Second thing, if you flash supersu on stock rom it won't boot due some security measures of Moto. Instead flash ElementalX kernel first and then flash supersu.
Click to expand...
Click to collapse
i'm really sorry about posting in wrong thread.
While trying to flash ElementalX kernel through memory card, I'm getting error: Zip signature verification failed, (in red).
nazim7 said:
All information that you will need can be found here. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
For the latest stock nougat firmware for XT1643 check this link https://mega.nz/#!ystC2ZSL!ql6cyC5v5RgLQfo7G44mhi7Ng-AQBvtsouKxKinbHi8
If you have some confusion about flashing, be sure to check it out before going on. I believe you have some knowledge about fastboot and using it.
Click to expand...
Click to collapse
Last time I used fastboot was more than one year ago. Also, my device is not being detected by adb when in bootloader.
d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
d1nesh said:
Last time I used fastboot was more than one year ago. Also, my device is not being detected by adb when in bootloader.
Click to expand...
Click to collapse
What did you mean by your device not being detected in bootloader mode. Did you install the right drivers. Did you install minimal adb and fastboot. Can you do the below steps and tell me the result.
1. Download the drivers from here.
For Windows: http://www.devfiles.co/download/5eEx...ager_2.5.4.exe
2. Download the Minimal ADB and Fastboot = https://www.androidfilehost.com/?fid=745425885120698566
3. Install Minimal ADB and Fastboot = https://forum.xda-developers.com/sho....php?t=2317790
4. Restart the Moto G4 in fastboot mode. (Bootloader mode)
5. Connect the Phone to the computer.
6. In adb fastboot folder shift+right click and then in the pop up click "open command window here"
7. In the command line type: "fastboot devices"
Seeing your serial number means we know all is good and your phone is connected and you can go on flash the stock firmware. If the serial number is not showing, the drivers are not properly installed.
---------- Post added at 01:33 PM ---------- Previous post was at 01:25 PM ----------
avirk said:
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
Click to expand...
Click to collapse
I thought he don't have TWRP installed. If TWRP is installed, then go on with what he said. That is the best solution for you. :good:
avirk said:
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
Click to expand...
Click to collapse
I tried the same, but the flashing process is stuck on "Patching system image unconditionally..." I tried two different ROMs, and in both cases, it is stuck in the same step
d1nesh said:
I tried the same, but the flashing process is stuck on "Patching system image unconditionally..." I tried two different ROMs, and in both cases, it is stuck in the same step
Click to expand...
Click to collapse
Try with wiping everything, wipe system and internal storage as well, I know your important data will be gone but it will be worth a try. If anything comes up let us know, also what have you tried so far tell us in details so we don't repeat it over and over, also in above post some links are provided try them.
avirk said:
Try with wiping everything, wipe system and internal storage as well, I know your important data will be gone but it will be worth a try. If anything comes up let us know, also what have you tried so far tell us in details so we don't repeat it over and over, also in above post some links are provided try them.
Click to expand...
Click to collapse
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
d1nesh said:
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
Click to expand...
Click to collapse
Try with other pc or change the port for data cable. It seems your system partition got corrupted, also you can mount system partition under twrp and then try to format it.
d1nesh said:
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
Click to expand...
Click to collapse
When in TWRP, go to Mount and see if system is ticked or not. If not, mount the system and wipe it. Then flash the rom again. BTW which TWRP version are you using. From where you get it.
nazim7 said:
When in TWRP, go to Mount and see if system is ticked or not. If not, mount the system and wipe it. Then flash the rom again. BTW which TWRP version are you using. From where you get it.
Click to expand...
Click to collapse
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
d1nesh said:
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
Click to expand...
Click to collapse
So that is the problem. You have to install TWRP latest version. Version 3.0.2 r4 or higher by shreps will work for you. You can find it here. https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
The latest version is 3.0.3 n4. Flash it, mount the system and everything will be good for you
d1nesh said:
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
Click to expand...
Click to collapse
As @nazim7 suggested you to flash the latest TWRP and then try to flash the rom again, also you can try to resize the partition and try to format it from twrp from the option in twrp. Just let us know what the result come back.
nazim7 said:
So that is the problem. You have to install TWRP latest version. Version 3.0.2 r4 or higher by shreps will work for you. You can find it here. https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
The latest version is 3.0.3 n4. Flash it, mount the system and everything will be good for you
Click to expand...
Click to collapse
There's one more problem like I've mentioned previously. I have the latest drivers even then the device is not being detected via adb when in bootloader, but as soon as I boot into recovery, the device shows up on adb after command. How do I flash the recovery if the device doesn't show up in bootloader on adb?
I tried to restored a nandroid backup which didnt work, I then tried to lock and unlock bootloader thinking recovery would reset original image and that didnt work and now its wiped. Any suggestions as I'm looping into bootloader screen and I cant even push an image using adb.
Have you tried formatting your data in TWRP?
sting5566 said:
Have you tried formatting your data in TWRP?
Click to expand...
Click to collapse
Yes. But I have no way so far to get an oxygen os rom to my internal storage so I can flash. Just keeps going to fastboot mode.
Did you try reinstalling Twrp thru fastboot?
sting5566 said:
Did you try reinstalling Twrp thru fastboot?
Click to expand...
Click to collapse
How would that help if I have nothing to flash? I can get to twrp no problem.
SysAdmNj said:
How would that help if I have nothing to flash? I can get to twrp no problem.
Click to expand...
Click to collapse
You stated it kept going back into fastboot, sorry if I misunderstood. Your PC should see the phone while in TRWP, try another port on your PC or another cable.
sting5566 said:
You stated it kept going back into fastboot, sorry if I misunderstood. Your PC should see the phone while in TRWP, try another port on your PC or another cable.
Click to expand...
Click to collapse
Yes, my phone is wiped and no OS on it either. Thats probably why its going back to fastboot. Is my only choice to unbrick? Which as I'm seeing would require me to go to hydrogen os before even being able to go to oxygen os?
SysAdmNj said:
Yes, my phone is wiped and no OS on it either. Thats probably why its going back to fastboot. Is my only choice to unbrick? Which as I'm seeing would require me to go to hydrogen os before even being able to go to oxygen os?
Click to expand...
Click to collapse
Even with it wiped, if you have TWRP installed and no OS you should still boot back into recovery, not fastboot. I would still try installing TWRP again, use the codeworkx version, seems to work best for most people.
sting5566 said:
Even with it wiped, if you have TWRP installed and no OS you should still boot back into recovery, not fastboot. I would still try installing TWRP again, use the codeworkx version, seems to work best for most people.
Click to expand...
Click to collapse
Ok so I'm definitely not understanding, once I install twrp codeworkx version then whats my next step to get my device up and running?
SysAdmNj said:
Ok so I'm definitely not understanding, once I install twrp codeworkx version then whats my next step to get my device up and running?
Click to expand...
Click to collapse
After that I would format data in TWRP, reboot back into TWRP and then copy over a rom. Your PC should see the phone plugged in booted up in TWRP.
sting5566 said:
After that I would format data in TWRP, reboot back into TWRP and then copy over a rom. Your PC should see the phone plugged in booted up in TWRP.
Click to expand...
Click to collapse
You mean I can copy OS 5.0.1 and flash directly to it after I copy it over?
Nevermind it worked, thanks. My whole issue was I didnt know the whole time that my pc would see the device as a directory while in twrp. Now I wonder why originally I booted into a black screen bricked when I flashed magisk 14 earlier.
SysAdmNj said:
You mean I can copy OS 5.0.1 and flash directly to it after I copy it over?
Nevermind it worked, thanks. My whole issue was I didnt know the whole time that my pc would see the device as a directory while in twrp. Now I wonder why originally I booted into a black screen bricked when I flashed magisk 14 earlier.
Click to expand...
Click to collapse
Glad it worked out for you. What rom were you trying to flash and why magisk 14, newer ones are out now.
sting5566 said:
Glad it worked out for you. What rom were you trying to flash and why magisk 14, newer ones are out now.
Click to expand...
Click to collapse
OOS 5.0.1 latest version of oreo for oneplus 5 is what I flashed and running now. Now I'm attemping to flash magisk, latest version and hopefully dont run into the black screen.
SysAdmNj said:
OOS 5.0.1 latest version of oreo for oneplus 5 is what I flashed and running now. Now I'm attemping to flash magisk, latest version and hopefully dont run into the black screen.
Click to expand...
Click to collapse
The latest xXx rom is close to stock and runs great if you want to try something custom.
SysAdmNj said:
You mean I can copy OS 5.0.1 and flash directly to it after I copy it over?
Nevermind it worked, thanks. My whole issue was I didnt know the whole time that my pc would see the device as a directory while in twrp. Now I wonder why originally I booted into a black screen bricked when I flashed magisk 14 earlier.
Click to expand...
Click to collapse
It's a known issue. You have to use Magisk 15.2 or higher.
If you flash an older version you will get a black screen with a blue notification led.
maikvitesse said:
It's a known issue. You have to use Magisk 15.2 or higher.
If you flash an older version you will get a black screen with a blue notification led.
Click to expand...
Click to collapse
Yes, I learned the hard way
I thought I could flash 14 and just update to 15.2.
sting5566 said:
The latest xXx rom is close to stock and runs great if you want to try something custom.
Click to expand...
Click to collapse
I actually want to stay close to stock. I dont even want to use nova launcher, I"m staying with OP launcher. So far so good, Not sure upgrade was worth the trouble yet
Hello all,
THIS IS AN ANNOUNCEMENT, DISCUSSION AND INFORMATION THREAD FOR OFFICIAL DIRTY UNICORNS 14.x BUILDS FOR PIXEL 2 XL (taimen).
Special thanks to all who were and are involved in the development and also to the maintenance of this ROM.
Flashing instructions:
Go to TWRP
Factory reset
Flash ROM and TWRP zip
Reboot and enjoy!!
If on a previous DU build:
Go to TWRP
Flash ROM and TWRP zip
Reboot and enjoy!!
Note:
If you're going to flash magisk make sure you flash it after you've booted the OS once.
Reminder
Weeklies and official builds are signed with private keys. This means that if you’re on the first official build or last week’s weekly, you can dirty flash this official build. If you’re on anything other than that and want to use this build you MUST perform a full wipe in recovery. If you decide to disregard this and flash this build or a weekly on top of anything, you will not be able to boot. Have fun looking at a black screen
ANY BUGS MAY BE DISCUSSED HERE OR WITH THE DEVELOPMENT TEAM ON THEIR TELEGRAM CHANNELONLY IF YOU HAVE CLEAN FLASHED
Reserved
its an excellent rom! i helped test here n there n can confirm its almost completely bug free
elliwigy said:
its an excellent rom! i helped test here n there n can confirm its almost completely bug free
Click to expand...
Click to collapse
Can you tell how is the camera quality on that?
And they have listed audi during video is janky is that for stock camera or for apps like whatsapp and snapchat too?
Sent from my Google Pixel 2 XL using XDA Labs
Been waiting very impatiently for this lol
Prattham said:
Can you tell how is the camera quality on that?
And they have listed audi during video is janky is that for stock camera or for apps like whatsapp and snapchat too?
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Just might be seldom janky...not all the time...I've tested stock DU cam, WhatsApp, Facebook, Instagram.... all working fine on all 3 different occasions:good:
Cam quality is as good as stock
No hangups...lags...or other issues
I will be using it as my daily driver
amandeepparmar said:
Just might be seldom janky...not all the time...I've tested stock DU cam, WhatsApp, Facebook, Instagram.... all working fine on all 3 different occasions:good:
Cam quality is as good as stock
No hangups...lags...or other issues
I will be using it as my daily driver
Click to expand...
Click to collapse
Can you post screenshot of the du tweaks that are currently in the rom?
Sent from my Google Pixel 2 XL using XDA Labs
Prattham said:
Can you post screenshot of the du tweaks that are currently in the rom?
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
DU Tweaks...check screenshots attached
amandeepparmar said:
DU Tweaks...check screenshots attached
Click to expand...
Click to collapse
Good
What steps did you followed to install?
Cheers ?
Sent from my Google Pixel 2 XL using XDA Labs
amandeepparmar said:
DU Tweaks...check screenshots attached
Click to expand...
Click to collapse
Factory reset in twrp. flash rom and twrp. Setup phone and flash afterwards kernel and magisk if needed
Anyone know if it has support for esim on Fi?
Flashing this will remove TWRP and Magisk. Just wanted to throw that out there.
MacTheRipperr said:
Flashing this will remove TWRP and Magisk. Just wanted to throw that out there.
Click to expand...
Click to collapse
Yes it will according to what I've been reading. I just got my pixel and have been trying to catch up with all the new a and b slots and how recovery is now baked into the boot.img, so from what I understand is that if you flash anything new such as rom or kernel a flash of both twrp and your choice of root is needed also or you will have stock recovery. So much different from my Nexus 6P. Lol. I have a lot to learn that's for sure
Sent from my Pixel 2 XL using XDA-Developers Legacy app
This rom is awesome !! DU always bring the goods
I've been running since yesterday. Spaceman killed it! Amazing work, where can we donate?
MacTheRipperr said:
Flashing this will remove TWRP and Magisk. Just wanted to throw that out there.
Click to expand...
Click to collapse
Yes but you can reflash twrp and magisk with absolutely no errors ,also twrp has no touch issues with the kernal that's already baked in rom!!!! It's a great rom!
Anyone else having trouble getting this to boot?
I've followed the instructions exactly. Reboot to TWRP (3.2.1-0), factory reset via the wipe menu, install the ROM .zip followed by the TWRP installer zip.
Go to reboot, TWRP asks me if I'm sure I want to do this as there's not an OS installed. I don't know what else to do other than say 'yes' and then it boots to the Google logo with the unlocked icon at the bottom of the screen and just hangs indefinitely at that point. Tried redownloading and recopying the ROM .zip to internal storage and all steps again too.
Any ideas? I've wiped this damn phone so many times and flashed the factory images so many times trying to get a custom ROM to work I'm about to give up. And my phone seems to damn janky where sometimes it does that same freeze on boot (or freezes on the TWRP splash screen) but then a quick reboot will fix it. Doesn't make any sense.
ohlin5 said:
Anyone else having trouble getting this to boot?
I've followed the instructions exactly. Reboot to TWRP (3.2.1-0), factory reset via the wipe menu, install the ROM .zip followed by the TWRP installer zip.
Go to reboot, TWRP asks me if I'm sure I want to do this as there's not an OS installed. I don't know what else to do other than say 'yes' and then it boots to the Google logo with the unlocked icon at the bottom of the screen and just hangs indefinitely at that point.
Any ideas? I've wiped this damn phone so many times and flashed the factory images so many times trying to get a custom ROM to work I'm about to give up. And my phone seems to damn janky where sometimes it does that same freeze on boot (or freezes on the TWRP splash screen) but then a quick reboot will fix it. Doesn't make any sense.
Click to expand...
Click to collapse
I went back to latest stock using deuces script. Boot twrp. Flash twrp then the rom...boot the rom. Go back into twrp and flash magisk
I had no problems getting it to boot, I followed the op. Factory reset, flash ROM, flash magisk, flash twrp and boot into system. It booted right up no problems
Sent from my Pixel 2 XL using XDA-Developers Legacy app
Reuben_skelz92 said:
I went back to latest stock using deuces script. Boot twrp. Flash twrp then the rom...boot the rom. Go back into twrp and flash magisk
Click to expand...
Click to collapse
Did you let the phone do it's initial boot after deuce's script ran? Or just stayed in fastboot mode, fastboot booted to TWRP, and flash the ROM and TWRP installer zip?
Also, did you format userdata when given the option in deuce's script? And you flashed TWRP before the ROM? I was under the understanding that the ROM flash would erase the TWRP install.
EDIT: I didn't format userdata, didn't reboot afterwards (just booted straight into TWRP and proceeded), and flashed TWRP before ROM and now it is indeed booting. Just need to figure out now whether or not TWRP is still installed. Many thanks! Deuce's must have fixed something I must have janked I guess.
EDIT2: Yeah appears TWRP should be flashed after the ROM not (just) before like the DU post says. I'm back to stock recovery afterwards.
Hey everyone, I need some help.
I have Magisk installed, and wanted to preserve root acces throughout the update (may security patch, ~80MB). I used this guide to do it, uninstalled Magisk, installed it on 2nd slot during phase 2, rebooted: bootloop. Stuck in an endless cycle: the kernel loads, but always reboots during the andorid one boot animation.
I'm looking for a way to make it functional while not losing my data, or a way to copy my data to a PC before flashing.
What can I do now?
Thanks in advance.
Flash stock ROM
Flash stock ROM through the MI FLASH TOOL..... download old version ROM through the XDA site nd flash it through MI FLASH TOOL also u can watch process on YouTube ....
Indiangautam said:
Flash stock ROM through the MI FLASH TOOL..... download old version ROM through the XDA site nd flash it through MI FLASH TOOL also u can watch process on YouTube ....
Click to expand...
Click to collapse
Will this preserve or wipe my data? I'm looking for a way that'll preserve my data.
droidx8 said:
Will this preserve or wipe my data? I'm looking for a way that'll preserve my data.
Click to expand...
Click to collapse
According to me no way to recover your data....if you flash stock ROM then all data will be wipe.....
Indiangautam said:
According to me no way to recover your data....if you flash stock ROM then all data will be wipe.....
Click to expand...
Click to collapse
Well let's not do that then, there could be another way... Thanks anyway!
droidx8 said:
Well let's not do that then, there could be another way... Thanks anyway!
Click to expand...
Click to collapse
As you wish....but if want to try my process then definitely your phone will bootup
droidx8 said:
Well let's not do that then, there could be another way... Thanks anyway!
Click to expand...
Click to collapse
You can choose to not wipe your data.
It's the "flash all except storage.bat"
You can download the last firmware here
http://en.miui.com/getrom.php?r=333&m=yes&app=false
You must have fastboot on your PC windows or Linux
So if you have a Windows just search how to install fastboot on Windows there's some great one on xda
Unzip the firmware open the flash all except storage bat
Remove both lines that contains
-OEM unlock
-OEM lock
Otherwise your data will be wiped and as you use magisk you want an unlocked bootloader
Open a powershell windows where the .bat file is
Then type without the quotes
"./flash_all_except_storage.bat"
Flashing procedure will take a few minutes on system partition but don't freak out
Once it's done reboot you'll be on 9.5.11 ROM version
You'll receive a 60mb ota to have the last one which is 9.11.13
You can boot TWRP to flash magisk now
And on next update download the last firmware
9.5.13 should be on the first link I gave you (there is always a delay between ota that are just patch and a full firmware that contains all the files)
Flash the boot.img or just reflash the ROM like above apply ota and reflash magisk
I ended up in the same situation but I think it's a technical problem where magisk is not concern I will not go into details but anyway this method is safe
JUST NEVER FORGET TO REMOVE THE OEM LOCK AND UNLOCK LINES since may update this will factory reset phone
ALWAYS USE THE "flash_all_except_storage" file
If you have some more questions I'm there
Dead-neM said:
You can choose to not wipe your data.
It's the "flash all except storage.bat"
I ended up in the same situation but I think it's a technical problem where magisk is not concern I will not go into details but anyway this method is safe
JUST NEVER FORGET TO REMOVE THE OEM LOCK AND UNLOCK LINES since may update this will factory reset phone
ALWAYS USE THE "flash_all_except_storage" file
If you have some more questions I'm there
Click to expand...
Click to collapse
Many thanks bro, worked perfectly! I haven't really kept up with android since 5.1, and now it's a bit hard to get back on track.
Data is intact, nothing lost, and the device is up and running.
droidx8 said:
Many thanks bro, worked perfectly! I haven't really kept up with android since 5.1, and now it's a bit hard to get back on track.
Data is intact, nothing lost, and the device is up and running.
Click to expand...
Click to collapse
Really nice to hear. Have fun with this little Beasty device