Ok every time I flash rom it boots to boolaoder.
Instructions
Wipe dalvik cache,cache,data.
Flash rom then install then reboot then setup finish then reboot.flash kernel optional then magisk.
Can't get pass bootloader . Ease help thx and happy new yr to all
Sent from my Pixel 3 XL using Tapatalk
freddienuxx said:
Ok every time I flash rom it boots to boolaoder.
Instructions
Wipe dalvik cache,cache,data.
Flash rom then install then reboot then setup finish then reboot.flash kernel optional then magisk.
Can't get pass bootloader . Ease help thx and happy new yr to all
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
What rom are you flashing? And what is reboot.flash? Try flashing the rom and then twrp if you want to keep that, I'd recommend you do. Then boot into system to see if it's working ok. Then if it is go back and flash the kernel and magisk.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
What rom are you flashing? And what is reboot.flash? Try flashing the rom and then twrp if you want to keep that, I'd recommend you do. Then boot into system to see if it's working ok. Then if it is go back and flash the kernel and magisk.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'm trying to flash bootlegger rom. Instructions say factory reset then flash rom then.setup device. Then reboot to twrp flash kernel then magisk. I tried with other rooms same thing stuck in bootloader. @jd1639 what rom are you on? And also how do you flash rom?
Sent from my Pixel 3 XL using Tapatalk
freddienuxx said:
I'm trying to flash bootlegger rom. Instructions say factory reset then flash rom then.setup device. Then reboot to twrp flash kernel then magisk. I tried with other rooms same thing stuck in bootloader. @jd1639 what rom are you on? And also how do you flash rom?
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I'm currently on stock rom with Kirisakura Kernel, but I have used bootlegger and it works for me.
After you flash the rom and boot into system does it just boot to the bootloader? If it does then I would start over by flashing the factory image with the flash-all batch file with the -w removed. Then make sure it boots into the system. Then I'd boot twrp, wipe the device, install the rom, then install twrp and boot to system. If it boots then boot back into recovery, twrp, and flash magisk. I don't know what kernel you are trying to flash but I believe bootlegger includes the Kirisakura Kernel. I'm very impressed with this kernel so I would not try to flash another one. If you are flashing a different kernel which one is it? It's possible that the kernel is not compatible with the bootlegger rom and that is what is causing your device to only boot to the bootloader.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'm currently on stock rom with Kirisakura Kernel, but I have used bootlegger and it works for me.
After you flash the rom and boot into system does it just boot to the bootloader? If it does then I would start over by flashing the factory image with the flash-all batch file with the -w removed. Then make sure it boots into the system. Then I'd boot twrp, wipe the device, install the rom, then install twrp and boot to system. If it boots then boot back into recovery, twrp, and flash magisk. I don't know what kernel you are trying to flash but I believe bootlegger includes the Kirisakura Kernel. I'm very impressed with this kernel so I would not try to flash another one. If you are flashing a different kernel which one is it? It's possible that the kernel is not compatible with the bootlegger rom and that is what is causing your device to only boot to the bootloader.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ok yea the furthest I get is after I flash bootlegger rom then twrp then I reboot to system that's when it goes straight to bootloader. I usually flash kernel and magisk after setup
Sent from my Pixel 3 XL using Tapatalk
freddienuxx said:
Ok yea the furthest I get is after I flash bootlegger rom then twrp then I reboot to system that's when it goes straight to bootloader. I usually flash kernel and magisk after setup
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Start over by flashing the factory image, or at least the boot image to both slots. Boot is probably messed up right now. I'd flash the whole image as I suggested as some times system and other partitions get messed up too.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Start over by flashing the factory image, or at least the boot image to both slots. Boot is probably messed up right now. I'd flash the whole image as I suggested as some times system and other partitions get messed up too.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
You think I should wipe the data?
Sent from my Pixel 3 XL using Tapatalk
freddienuxx said:
You think I should wipe the data?
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
No need to wipe data. When you to flash the rom I'd use the default wipe in twrp. Make a backup of the data partition in twrp before you wipe the device and store it off the device. You restore that after flashing the rom.
Sent from my [device_name] using XDA-Developers Legacy app
Related
If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?
You need to decrypt the phone for it to work.
Hmm anyone got the 7.0 recovery? I installed it thinking it would work but I want to keep the system encrypted. Does the stock 7.0 recovery mount system? I want to mod my build.prop dpi.
trollyphysicist said:
If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?
Click to expand...
Click to collapse
Try TWRP 3.0.2-1, should work properly.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Try TWRP 3.0.2-1, should work properly.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I just tried 3.0.2-1, and it worked. Before that, 3.0.2-0 also got stuck at the splash screen. However, I wasn't able to root. I tried installing SU via TWRP, but it didn't successfully root.
pkadavid said:
I just tried 3.0.2-1, and it worked. Before that, 3.0.2-0 also got stuck at the splash screen. However, I wasn't able to root. I tried installing SU via TWRP, but it didn't successfully root.
Click to expand...
Click to collapse
I had no issues obtaining root with the new twrp on an encrypted phone.
Am I the only one who encounters the flasing of recovery not sticking? After system reboot, then going back to recovery, it reverts to stock.
legendarren said:
Am I the only one who encounters the flasing of recovery not sticking? After system reboot, then going back to recovery, it reverts to stock.
Click to expand...
Click to collapse
Flash twrp, while still in bootloader volume down to reboot bootloader, hit the power button, volume down to reboot recovery, hit the power button. Twrp should stick now.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
Flash twrp, while still in bootloader volume down to reboot bootloader, hit the power button, volume down to reboot recovery, hit the power button. Twrp should stick now.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks, man. But still TWRP still doesn't stick after system reboot.
legendarren said:
Thanks, man. But still TWRP still doesn't stick after system reboot.
Click to expand...
Click to collapse
If you decrypt it first by flashing the modified boot.img, and then flash recovery and reboot it should stick and work right? Can you kindly describe your steps?
Vanschtezla said:
If you decrypt it first by flashing the modified boot.img, and then flash recovery and reboot it should stick and work right? Can you kindly describe your steps?
Click to expand...
Click to collapse
Yes, I forgot about decrypting. It works fine now, thanks!!
legendarren said:
Yes, I forgot about decrypting. It works fine now, thanks!!
Click to expand...
Click to collapse
No problem mate ??
Vanschtezla said:
No problem mate ??
Click to expand...
Click to collapse
Which boot IMG did you use to decrypt the final release of n?
kevtrysmoddin said:
Which boot IMG did you use to decrypt the final release of n?
Click to expand...
Click to collapse
In my case I updated mine from DP5. I had my DP5 decrypted and rooted and update it using the flashfire app to flash the ota. I don't think any of the existing modified boot.img will work on the final release yet idk mate.
Vanschtezla said:
In my case I updated mine from DP5. I had my DP5 decrypted and rooted and update it using the flashfire app to flash the ota. I don't think any of the existing modified boot.img will work on the final release yet idk mate.
Click to expand...
Click to collapse
No probs
trollyphysicist said:
If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?
Click to expand...
Click to collapse
Just installed twrp and seeing if flashign super su stuck or not... Have to wait for modified boot images to decrypt, though
---------- Post added at 10:25 AM ---------- Previous post was at 10:14 AM ----------
trollyphysicist said:
If I upgrade to 7.0 on my nexus 5x, will i be able to install twrp as i normally would through fastboot?
Click to expand...
Click to collapse
Update-phone is decrypted after installing twrp, wiping userdate, rebooting twrp, flashing latest super su, rebooting
eggman618 said:
Hmm anyone got the 7.0 recovery? I installed it thinking it would work but I want to keep the system encrypted. Does the stock 7.0 recovery mount system? I want to mod my build.prop dpi.
Click to expand...
Click to collapse
3.0.2-1 TWRP that got released soon after I posted fixed any hanging issues.
eggman618 said:
3.0.2-1 TWRP that got released soon after I posted fixed any hanging issues.
Click to expand...
Click to collapse
-1 installs, but two issues if you're encrypted:
1) TWRP doesn't stick. After a restart, you won't be able to get back into TWRP and need to reflash it.
2) Installing SU via TWRP doesn't work. It runs into an error if you read the responses during the flash in TWRP.
We'll just have to be patient until the devs do their magic on the encrypted version.
pkadavid said:
-1 installs, but two issues if you're encrypted:
1) TWRP doesn't stick. After a restart, you won't be able to get back into TWRP and need to reflash it.
2) Installing SU via TWRP doesn't work. It runs into an error if you read the responses during the flash in TWRP.
We'll just have to be patient until the devs do their magic on the encrypted version.
Click to expand...
Click to collapse
If you root using phh's superuser and magisk, TWRP will stick. His solution also allows you to use Android Pay with root, albeit with a little hoop-jumping
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
I had the twrp not sticking issue in the past. What has worked is to boot twrp, not flash it, then flash SU. Then boot back into the bootloader and flash twrp.
Sent from my Nexus 9 using XDA-Developers mobile app
Sorry for the noob question.
I have upgraded my 5X to 7.0 and flashed a custom recovery and kernel. Everything went fine but I would like to try other kernels. A lot of the custom kernels say they should only be flashed on the original stock kernel. Where can I download the stock kernel and is it as straight forward as flashing the custom builds?
TIA
purpse said:
Sorry for the noob question.
I have upgraded my 5X to 7.0 and flashed a custom recovery and kernel. Everything went fine but I would like to try other kernels. A lot of the custom kernels say they should only be flashed on the original stock kernel. Where can I download the stock kernel and is it as straight forward as flashing the custom builds?
TIA
Click to expand...
Click to collapse
In TWRP, backup only boot.img and name it appropriately. Now flash your custom kernel. Each time you want to switch custom kernels while on the stock rom, reflash that boot.img.
To switch custom kernels while on custom roms, dirty flash your rom then flash the custom kernel. Dirty flashing (no wipe) restores the boot.img that ships with the custom rom.
Sent from my Nexus 5X using Tapatalk
Thanks. Do I flash kernel followed boot.img or other way round ir or does it not matter?
Sorry I read your post wrong. I didn't backup boot while on stock so I will need to go back to stock everything first
purpse said:
Sorry I read your post wrong. I didn't backup boot while on stock so I will need to go back to stock everything first
Click to expand...
Click to collapse
Or download the factory image from Google and pull the boot.img from the zip.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Or download the factory image from Google and pull the boot.img from the zip.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Hmm, I just did this as well.
With ElementalX I was stuck on the android loading screen (bouncing bubbles)
Now after flashing boot.img from google, I"m stuck on the black "Google"
derrickl1990 said:
Hmm, I just did this as well.
With ElementalX I was stuck on the android loading screen (bouncing bubbles)
Now after flashing boot.img from google, I"m stuck on the black "Google"
Click to expand...
Click to collapse
Try flashing the boot and system image.
Sent from my Nexus 5X using Tapatalk
I found 2 versions of the instruction about going back from custom ROM to stock OxygenOS. First one tells about ADB commands which results with full stock, with standard recovery, unrooted system and locked phone. The second one is shorter, it's just flashing official zip with TWRP.
So my question is: Am I "losing something" after going with the second option, I mean TWRP-way? As I understand the only difference is that I'll keep TWRP itself and my phone will still be unlocked, when everything else will be ok (official camera firmware, kernel, etc.).
Thank you in advance for the answer if I'm wrong
The official zips in most cases also erase your twrp recovery and you will end up with the stock recovery and unlocked bootloader
I'm also thinking about going back to Oxygenos. But haven't done it. Looking for answers for you question.
Besides, could you please give me the link for the first method? Thanks
It's like flashing any other Rom? You clean flash by wiping everything (except Internal) and flash the OxygenOS you want (plus SuperUser).
Heres what you gonna do
Download oos full zip
Flash it on twrp then after that dont do a reboot just flash twrp as recovery then reboot to recovery and then reboot to system
If you wanna lock the bootloader and stay fully stock ( this will wipe your whole phone so backup )
Then flash oos full zip through twrp then reboot to bootloader
Then sideload oos recovery
Then go back to bootloader and relock bootloader thats it
Sent from my ONEPLUS A3003 using Tapatalk
You want to ADB push?
Go to OnePlus site. There you have step by step instructions.
HIshan Pavidu said:
Heres what you gonna do
Download oos full zip
Flash it on twrp then after that dont do a reboot just flash twrp as recovery then reboot to recovery and then reboot to system
If you wanna lock the bootloader and stay fully stock ( this will wipe your whole phone so backup )
Then flash oos full zip through twrp then reboot to bootloader
Then sideload oos recovery
Then go back to bootloader and relock bootloader thats it
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
I want to keep twrp and stay unlocked
1. flash the oos full zip
2. reboot to fastboot mode and flash twrp
3. go to twrp and reboot to system
Is this right?
Besides, I'm using twrp 3.0.4-1. Does it matter?
JonathanKang said:
I want to keep twrp and stay unlocked
1. flash the oos full zip
2. reboot to fastboot mode and flash twrp
3. go to twrp and reboot to system
Is this right?
Besides, I'm using twrp 3.0.4-1. Does it matter?
Click to expand...
Click to collapse
They both works but my way dont need a pc so
Sent from my ONEPLUS A3003 using Tapatalk
HIshan Pavidu said:
They both works but my way dont need a pc so
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Ahh. Got it.
JonathanKang said:
Ahh. Got it.
Click to expand...
Click to collapse
Good luck huh!
Sent from my ONEPLUS A3003 using Tapatalk
HIshan Pavidu said:
Good luck huh!
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
I clean flashed the full zip. When I try to boot to bootloader, it didn't enter bootloader mode. The system boots, and it's been showing boot animation for more than ten minutes. I'll wait patiently.
BTW, how do you flash twrp while you are in twrp?
JonathanKang said:
I clean flashed the full zip. When I try to boot to bootloader, it didn't enter bootloader mode. The system boots, and it's been showing boot animation for more than ten minutes. I'll wait patiently.
BTW, how do you flash twrp while you are in twrp?
Click to expand...
Click to collapse
What i did was
Flashed the full zip
Before rebooting flashed twrp.img through twrp
Then reboot to twrp abd reboot to system i do it every time
Sent from my ONEPLUS A3003 using Tapatalk
HIshan Pavidu said:
What i did was
Flashed the full zip
Before rebooting flashed twrp.img through twrp
Then reboot to twrp abd reboot to system i do it every time
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
What I wanna ask is how do you flash twrp.img through twrp?
JonathanKang said:
What I wanna ask is how do you flash twrp.img through twrp?
Click to expand...
Click to collapse
When your on twrp go to install then to the right corner youll see a tab named flash img clikc that and browse to your twrp flash it then it will ask system , recovery or bootloader click recovery then flash when it finished reboot to recovery
I hope you understand if not just google it
Sent from my ONEPLUS A3003 using Tapatalk
HIshan Pavidu said:
When your on twrp go to install then to the right corner youll see a tab named flash img clikc that and browse to your twrp flash it then it will ask system , recovery or bootloader click recovery then flash when it finished reboot to recovery
I hope you understand if not just google it
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Okay. Never notice that tab in the corner.
So right now, I end up with oxygenos(still booting...) without twrp.
JonathanKang said:
Okay. Never notice that tab in the corner.
So right now, I end up with oxygenos(still booting...) without twrp.
Click to expand...
Click to collapse
Try holding power button till it restart and see if you can load to bootloader then sideload twrp then do what i said
Good luck
If it wont load bootloader i think its bricked or something
Sent from my ONEPLUS A3003 using Tapatalk
HIshan Pavidu said:
Try holding power button till it restart and see if you can load to bootloader then sideload twrp then do what i said
Good luck
If it wont load bootloader i think its bricked or something
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Force shutdown the device and entered fastboot, flashed twrp recovery. And now twrp asks me to input password to decrypt data. I have no idea about what the password is. I also got dm-verity error after flashing the full zip. Help needed.
JonathanKang said:
Force shutdown the device and entered fastboot, flashed twrp recovery. And now twrp asks me to input password to decrypt data. I have no idea about what the password is. I also got dm-verity error after flashing the full zip. Help needed.
Click to expand...
Click to collapse
Im sorry i have to say this but you might wanna sideload oos recovery then sideload oos full zip and see if its boot then try again
Edit :- you might wanna wipe everything before sideload idk try without wiping anything
Sent from my ONEPLUS A3003 using Tapatalk
HIshan Pavidu said:
Im sorry i have to say this but you might wanna sideload oos recovery then sideload oos full zip and see if its boot then try again
Edit :- you might wanna wipe everything before sideload idk try without wiping anything
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
I did a factory reset in twrp, and the system boots well. But unfortunately I lost all my data. Factory reset also formats internal storage?
I have all my photos backed up in google photos. The only loss is the image quality is not original. Anyway it's not end of the world.
JonathanKang said:
I did a factory reset in twrp, and the system boots well. But unfortunately I lost all my data. Factory reset also formats internal storage?
I have all my photos backed up in google photos. The only loss is the image quality is not original. Anyway it's not end of the world.
Click to expand...
Click to collapse
Your good then right? Cuz i gotta go flash rr ?
Sent from my ONEPLUS A3003 using Tapatalk
Hi guys,
Today I've decided to update my Nexus 5x to the last Oreo official update.
I've flashed with fastboot the last factory image, and the modified "boot.img" for 4 cores (to avoid bootloop).
The phone booted but it's stuck at the spinning circles animation for almost an hour right now and I don't understand what I did wrong.
Before the flashing, I was running an old version of Pixel Rom (based on nougat)
I haven't used the 4 core boot.img but I do remember it was updated whenever a new image came out. You might check the thread for the 4 core boot.img to make sure you're using the one for the image you flashed.
Sent from my [device_name] using XDA-Developers Legacy app
I'm pretty sure that I've flashed the right boot.img for the factory image I've installed ..
Should I try wiping everything and re-flashing the factory image? How do I do it?
Use the flash-all batch file in the extracted factory image. That will wipe the device and flash all the partitions.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Use the flash-all batch file in the extracted factory image. That will wipe the device and flash all the partitions.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I did that half an hour ago but the phone is still stuck at the boot animation .. Should I try flashing twrp and an unofficial rom based on 8.1? Which is the best rom for the phone at the moment?
Here's what I would try, keep in mind I don't have the boot issue on my 5x so haven't had to face this problem. You may have already done this, but:
Flash each partition of the factory image separately with fastboot.
Then boot into the recovery provided with the 4 core image files, fastboot boot recovery.img (recovery.img is the full name of the recovery.
Copy the 4 core image file to your device while booted in to recovery. I'm assuming the recovery image is a modified version of twrp.
Then flash the boot image file in twrp
Cross your fingers and boot into system. Note that you'll still have the stock recovery (you haven't flashed it yet)
Indeed, the previous post summarizes the correct procedure.
Be sure to grab all the files (factory image, boot image, recovery image) for the last distribution from this post, and follow the previous post.
Flash factory image with flash-all, reboot (should be boot looping, so go to the bootloader), flash boot, flash recovery, wipe cache (not needed, but preferable), reboot and enjoy.
That did the trick for me just yesterday, while I had a similar problem to yours, where I tried flashing the boot image, and the phone was simply showing the animated android dots for hours. I'm not sure which step I missed, but this fixed it immediately (I did not wipe the cache).
Good luck.
Thank You guys I finally managed to make it boot on oreo 8.1
raiden99 said:
Thank You guys I finally managed to make it boot on oreo 8.1
Click to expand...
Click to collapse
Do you know what you did to finally get it going? It might help others.
Sent from my [device_name] using XDA-Developers Legacy app
raiden99 said:
Hi guys,
Today I've decided to update my Nexus 5x to the last Oreo official update.
I've flashed with fastboot the last factory image, and the modified "boot.img" for 4 cores (to avoid bootloop).
The phone booted but it's stuck at the spinning circles animation for almost an hour right now and I don't understand what I did wrong.
Before the flashing, I was running an old version of Pixel Rom (based on nougat)
Click to expand...
Click to collapse
I think I am in the same situation. How did you escape from the 4 running circles? Any key combination?
I am trying to go to recovery or fastboot bu the cyrcles are spinning and nothing is responding. I
xpact said:
I think I am in the same situation. How did you escape from the 4 running circles? Any key combination?
I am trying to go to recovery or fastboot bu the cyrcles are spinning and nothing is responding. I
Click to expand...
Click to collapse
If you continuoesly hold power and volume down will it boot into the bootloader?
Sent from my [device_name] using XDA-Developers Legacy app
xpact said:
I think I am in the same situation. How did you escape from the 4 running circles? Any key combination?
I am trying to go to recovery or fastboot bu the cyrcles are spinning and nothing is responding. I
Click to expand...
Click to collapse
Same question. How do you even escape out of the 4 running circles (besides waiting for the battery to drain and power off)?
I have something to say.. so like.. I tried to put many (ROMS) on my phone (Nexus 5X) right? found out lots of things.. I've bricked my phone, I've currently got a "your phone is currupted, blah blah blah" after I just installed android 6.0.1 very funny, cause it works almost fine... till it just keeps going to the boot animation, and starts... lolll I'm learning.. ill figure it out... just letting you know google.. has currupted (OTA Updates) LMAO, the latest one from them is fine, I'm probably gonna get AEX ROM though after, if I can get it to work (Edit.. like 5 mins later) I'm now flashing android 8.0.1 to install AEX.. I knew I was but didn't know when I was going to...
Yesterday i sideloaded the December ota, today i decided im going to unlock the bootloader, root and install a custom kernel. I followed the instructions in the pined post in guides and well, now my pixel wont boot and its booting back to trwp.
What i did was boot twrp.img thru fastboot.
Once twrp booted i flashed the twrp zip, kernel and magisk beta zip.
How do i get out of this bootloop now?
welp, just tried to flash the factory image and got this:
error: failed to load 'image-crosshatch-pq1a.181205.006.zip': Not enough space
mac208x said:
Yesterday i sideloaded the December ota, today i decided im going to unlock the bootloader, root and install a custom kernel. I followed the instructions in the pined post in guides and well, now my pixel wont boot and its booting back to trwp.
What i did was boot twrp.img thru fastboot.
Once twrp booted i flashed the twrp zip, kernel and magisk beta zip.
How do i get out of this bootloop now?
Click to expand...
Click to collapse
fastboot flash boot --slot all boot.img
#6 in this guide.
Homeboy76 said:
fastboot flash boot --slot all boot.img
#6 in this guide.
Click to expand...
Click to collapse
Thank you! So would you know what i did wrong? Or what do i now to get root and custom kernel?
mac208x said:
Thank you! So would you know what i did wrong? Or what do i now to get root and custom kernel?
Click to expand...
Click to collapse
Pixel 3/Pixel 3 XL
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- add more zips
- Edit: Kernel of your choice
- Add more zips
- magisk-17.3.zip
- reboot system
Homeboy76 said:
Pixel 3/Pixel 3 XL
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- add more zips
- ElementalX 1.02.zip
- Add more zips
- magisk-17.3.zip
- reboot system
Click to expand...
Click to collapse
Did exactly that but instead of ElementalX kernel im trying to use Kirisakura now back to bootloop into recovery
mac208x said:
Did exactly that but instead of ElementalX kernel im trying to use Kirisakura now back to bootloop into recovery
Click to expand...
Click to collapse
After installing the TWRP.zip change slots in TWRP, reboot recovery and flash Magisk to the other slot, change slots back, then reboot.
airmaxx23 said:
Change slots in TWRP, reboot recovery and flash Magisk to the other slot, change slots back, then reboot.
Click to expand...
Click to collapse
Im so sorry but what do you mean by slot?
mac208x said:
Im so sorry but what do you mean by slot?
Click to expand...
Click to collapse
When you're in TWRP go to reboot, then switch from your current slot to the other.
airmaxx23 said:
When you're in TWRP go to reboot, then switch from your current slot to the other.
Click to expand...
Click to collapse
Alright this is becoming silly. Did exactly as you said and again, bootloop back too twrp....Should i use the twrp from dees_troy or it doesnt matter? I dont know what it can be
Edit: Nvm im using the right twrp
mac208x said:
Alright this is becoming silly. Did exactly as you said and again, bootloop back too twrp....Should i use the twrp from dees_troy or it doesnt matter? I dont know what it can be
Edit: Nvm im using the right twrp
Click to expand...
Click to collapse
Are you flashing Magisk in both slots?
airmaxx23 said:
Are you flashing Magisk in both slots?
Click to expand...
Click to collapse
No didn't do that.
Okay so fastboot boot twrp.img
Once it boots flash the twrp.zip and magisk
Change to slot b
Flash magisk
Reboot.
Right? What about kernel?
mac208x said:
No didn't do that.
Okay so fastboot boot twrp.img
Once it boots flash the twrp.zip and magisk
Change to slot b
Flash magisk
Reboot.
Right? What about kernel?
Click to expand...
Click to collapse
Try just that first and see if you can fully boot the phone.
airmaxx23 said:
Try just that first and see if you can fully boot the phone.
Click to expand...
Click to collapse
No bootloop back to trwp. Now its stuck on the white google logo screen wont go pass it
airmaxx23 said:
When you're in TWRP go to reboot, then switch from your current slot to the other.
Click to expand...
Click to collapse
Be careful with that. I did it bricked the device. It was like there was no system on that slot. I thought it was hard bricked but someone else did the same thing and eventually got it to boot.
Sent from my [device_name] using XDA-Developers Legacy app
I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.
jd1639 said:
Be careful with that. I did it bricked the device. It was like there was no system on that slot. I thought it was hard bricked but someone else did the same thing and eventually got it to boot.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've been doing it all along whenever I flash anything.
mac208x said:
I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.
Click to expand...
Click to collapse
You'll have to flash back to stock in fastboot.
mac208x said:
I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.
Click to expand...
Click to collapse
First, have you updated your sdk platform tools with the latest fastboot and adb? That's been causing a lot of people problems if they haven't updated them. If you have I would flash the stock boot image to boot slots.
fastboot flash boot_a boot.img. and
fastboot flash boot_b boot.img
If that's not enough then flash the system's image to boot slots.
Sent from my [device_name] using XDA-Developers Legacy app
airmaxx23 said:
I've been doing it all along whenever I flash anything.
You'll have to flash back to stock in fastboot.
Click to expand...
Click to collapse
jd1639 said:
First, have you updated your sdk platform tools with the latest fastboot and adb? That's been causing a lot of people problems if they haven't updated them. If you have I would flash the stock boot image to boot slots.
fastboot flash boot_a boot.img. and
fastboot flash boot_b boot.img
If that's not enough then flash the system's image to boot slots.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
How do i do this now? Flashing boot.img does nothing, phone still wont boot and hands on the boot logo. I cant enter recovery and apply from adb, nor flashing the factory image thru fastboot work, it keeps saying there isnt enough space for the .zip
mac208x said:
How do i do this now? Flashing boot.img does nothing, phone still wont boot and hands on the boot logo. I cant enter recovery and apply from adb, nor flashing the factory image thru fastboot work, it keeps saying there isnt enough space for the .zip
Click to expand...
Click to collapse
Do you have the latest sdk platform tools. If not Google that, download the zip and extract it. Replace what you do have. I create a folder c:adb and put everything in that. Then set an environment variable path in Windows so fastboot and adb are available no matter what folder I'm working in.
Sent from my [device_name] using XDA-Developers Legacy app