search

phhusson / treble_experimentations

Notes about tinkering with Android Project Treble
3.38k stars 655 forks source link

Razer Phone 2 (Cheryl 2) Not Booting #742

Open fromeister2018 opened 5 years ago

fromeister2018 commented 5 years ago

I have twrp installed on my razer phone 2. I also had a deoxed razer phone 2 stock rom downloaded and installed and then downloaded android 10 v200.D. I factory reset the phone, then formatted the data, then flashed v200.D only and then the magisk zip and then reset the phone, and it goes into a boot loop. Not sure if I need to flash v200 and then flash v200.d as I have been unable to get any of these to get past either the powered by android screen or the bootloop.

DforDooM commented 5 years ago

removed to keep environment clean

phhusson commented 5 years ago

Gosh no don't do that. Use stock boot, not a custom boot, and no Magisk. You can have whatever you want in the other slot, but be sure to have a working vendor in the slot you're trying to boot...

Le lun. 14 oct. 2019 à 11:24, DforDooM notifications@github.com a écrit :

I dirty flashed 200.d on my RP2 and didn't have any issues. Try the steps below and report back your results.

Walkthrough for simplicity(assumes you're using _b for your 10 install, _a has Pie working, and fastboot is being used):

Note: Bromite WebView wont work for now it seems, so don't bother trying to install it if you DO get it booted until something changes or you're going to bootloop. If you do inevitably boot loop from one module or another don't panic. Get to your bootloop screen, on your PC do the following:

  • Open command prompt
  • "adb root"
  • "adb shell"
  • "su" for good measure and to see if things are working properly
  • "magisk" (if that doesn't work try "sh /sbin/.magisk/magisk"
  • if that works and you get the Magisk menu then do "magisk --remove-modules"
  • At that point your device will reboot and should come back up with no issues

If you are still unable to boot after following my instructions then post your logcat/syslog here and I'll attempt to assist. Also, I'm assuming you're aware of this, but you'll need to flash opengapps to get everything functional. I had a tough time finding the proper set of OpenGApps to use, so here https://sourceforge.net/projects/opengapps/files/arm64/beta/20191006/ is the link with all the different flavors you can choose from. For the record, I went with Full.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/742?email_source=notifications&email_token=AAAA4ORSFZV5AEQJXTFUX2TQOQ3EXA5CNFSM4I46IUWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBD4KTI#issuecomment-541574477, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OUKSIG2BVG4W7HMKWLQOQ3EXANCNFSM4I46IUWA .

DforDooM commented 5 years ago

The custom kernel is strictly for TWRP, and he didn't modify much of anything else as far as I can tell. Original directory structure is still in tact, no crazy custom settings, just some power/CPU/RAM performance tweaks and the TWRP. I'm not saying you're wrong of course, but it has worked well for me so I thought I'd share.

phhusson commented 5 years ago

But we're in an issue tracker, to track issues I need the environment to be as sane as possible. OEM boot image is sane because it passed Google certification, and I know there can't be mismatches. Custom boot image might be hard to ensure you are using it on correct vendor.

Also, if there is an issue with OEM boot image, I want to be aware of it.

Your recommendation is fine on user forums or such, just not here

Le lun. 14 oct. 2019 à 11:35, DforDooM notifications@github.com a écrit :

The custom kernel is strictly for TWRP, and he didn't modify much of anything else as far as I can tell. Original directory structure is still in tact, no crazy custom settings, just some power/CPU/RAM performance tweaks and the TWRP. I'm not saying you're wrong of course, but it has worked well for me so I thought I'd share.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/742?email_source=notifications&email_token=AAAA4OWS5XYSJXIN3E4XQJ3QOQ4NDA5CNFSM4I46IUWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBD5LMY#issuecomment-541578675, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OTH3RRSUGHYCC2BMPTQOQ4NDANCNFSM4I46IUWA .

DforDooM commented 5 years ago

But we're in an issue tracker, to track issues I need the environment to be as sane as possible. OEM boot image is sane because it passed Google certification, and I know there can't be mismatches. Custom boot image might be hard to ensure you are using it on correct vendor. Also, if there is an issue with OEM boot image, I want to be aware of it. Your recommendation is fine on user forums or such, just not here Le lun. 14 oct. 2019 à 11:35, DforDooM notifications@github.com a écrit : … The custom kernel is strictly for TWRP, and he didn't modify much of anything else as far as I can tell. Original directory structure is still in tact, no crazy custom settings, just some power/CPU/RAM performance tweaks and the TWRP. I'm not saying you're wrong of course, but it has worked well for me so I thought I'd share. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#742?email_source=notifications&email_token=AAAA4OWS5XYSJXIN3E4XQJ3QOQ4NDA5CNFSM4I46IUWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBD5LMY#issuecomment-541578675>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OTH3RRSUGHYCC2BMPTQOQ4NDANCNFSM4I46IUWA .

Edited my comment to remove it because you're correct. This isn't the place for chaotic variable testing.

phhusson commented 5 years ago

Well you could have left it for reference, I'm not that strict :p

DforDooM commented 5 years ago

Well you could have left it for reference, I'm not that strict :p

USE AT YOUR OWN RISK

(Also, don't ask Mr. Husson for assistance if you do this pls :) )

I dirty flashed 200.d on my RP2 and didn't have any issues. Try the steps below and report back your results.

Walkthrough for simplicity(assumes you're using _b for your 10 install, _a has Pie working, and fastboot is being used):

  • "fastboot flash boot_a arter97-r11.img"
  • "fastboot set_active a"
  • "fastboot reboot"
  • _Once booted into your existing Pie installation on systema, patch with Magisk 20.0
  • Disable all Magisk modules
  • "fastboot flash boot_b magiskpatched.img"
  • "fastboot flash system_b arm64-ab-10.img"
  • "fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img" (from your original factory image)
  • "fastboot set-active b"
  • "fastboot reboot"

Note: Bromite WebView wont work for now it seems, so don't bother trying to install it if you DO get it booted until something changes or you're going to bootloop. If you do inevitably boot loop from one module or another don't panic. Get to your bootloop screen, on your PC do the following:

  • Open command prompt
  • "adb root"
  • "adb shell"
  • "su" for good measure and to see if things are working properly
  • "magisk" (if that doesn't work try "sh /sbin/.magisk/magisk"
  • if that works and you get the Magisk menu then do "magisk --remove-modules"
  • At that point your device will reboot and should come back up with no issues

If you are still unable to boot after following my instructions then post your logcat/syslog here and I'll attempt to assist. Also, I'm assuming you're aware of this, but you'll need to flash opengapps to get everything functional. I had a tough time finding the proper set of OpenGApps to use, so here is the link with all the different flavors you can choose from. For the record, I went with Full.

fromeister2018 commented 4 years ago

the only thing that I am having an issue with is flashing OpenGApps, which I am getting an issue that says "gapps are out of scope" and that there is not enough room to install it

DforDooM commented 4 years ago

Hey man, lucky for you this is an easy one. Go to wipe, select your system partition, choose advanced, then choose resize partition. Now try to flash it again. :)