Help

[Mr. Blanco]

I was on February stock image with twrp and magisk and elemental X kernal installed prior and had everything functioning properly since the febuary update but just installed flux theme within substratum and when i applied overlay my screen went black with only status bar icons showing ...so i rebooted phone and for some reason it boots and hangs on the google loading page then boots to twrp ...unfortunatly i had password/fingerprint lock on so twrp wont decrypt , i tried using adb/fastboot to try and do a flash all bat but fastboot message says fastboot is not recongnized as an internal or external command , operable program or batch file ... i have the -w removed from the flash all bat , i'm wondering if it wont flash because adb setting isn't on in developer settings..... dont know what to do or how to fix :crying:
If anyone could help or offer advice it would be greatly appreciated

 

[Badger50]

I was on February stock image with twrp and magisk and elemental X kernal installed prior and had everything functioning properly since the febuary update but just installed flux theme within substratum and when i applied overlay my screen went black with only status bar icons showing ...so i rebooted phone and for some reason it boots and hangs on the google loading page then boots to twrp ...unfortunatly i had password/fingerprint lock on so twrp wont decrypt , i tried using adb/fastboot to try and do a flash all bat but fastboot message says fastboot is not recongnized as an internal or external command , operable program or batch file ... i have the -w removed from the flash all bat , i'm wondering if it wont flash because adb setting isn't on in developer settings..... dont know what to do or how to fix :crying:
If anyone could help or offer advice it would be greatly appreciated

Your likely going to have to do a clean flash of the factory image, and wipe it clean since you can't get into twrp to restore your backup. However, it also sounds like your device is not being recognized by adb/fastboot. When your in fastboot mode, and type fastboot devices, do you get your phone ID displayed?? Also, are your SDK/platform-tools up to date??

 

[Mr. Blanco]

Your likely going to have to do a clean flash of the factory image, and wipe it clean since you can't get into twrp to restore your backup. However, it also sounds like your device is not being recognized by adb/fastboot. When your in fastboot mode, and type fastboot devices, do you get your phone ID displayed?? Also, are your SDK/platform-tools up to date??

I'm using sdk platform tools dec, 27.0.1 so i believe it is the most up to date version and when i fastboot devices i do get a serial number - fastboot showing , which is what kind of confused me , did the flash all bat and got that message as i posted before and the only thing i have changed in it was removing the -w ... so kind of scratching my head here why it's not working ... do you have any ideas what i might be able to do to fix

 

[Badger50]

I'm using sdk platform tools dec, 27.0.1 so i believe it is the most up to date version and when i fastboot devices i do get a serial number - fastboot showing , which is what kind of confused me , did the flash all bat and got that message as i posted before and the only thing i have changed in it was removing the -w ... so kind of scratching my head here why it's not working ... do you have any ideas what i might be able to do to fix

Are you typing the command, or double clicking the script??
Your definitely up to date on SDK BTW ?

 

[Mr. Blanco]

Your likely going to have to do a clean flash of the factory image, and wipe it clean since you can't get into twrp to restore your backup. However, it also sounds like your device is not being recognized by adb/fastboot. When your in fastboot mode, and type fastboot devices, do you get your phone ID displayed?? Also, are your SDK/platform-tools up to date??

i'm really embarrassed ... i was using the flash all bat from with in the factory image and not the platform tools file .. i sincerely apologize for posting this thread , this was definitely a user error ....is there a way to delete this embarrassing thread ...lol

 

[Badger50]

i'm really embarrassed ... i was using the flash all bat from with in the factory image and not the platform tools file .. i sincerely apologize for posting this thread , this was definitely a user error ....is there a way to delete this embarrassing thread ...lol

Dude, there's nothing to be embarrassed about, most of us have been there, no big deal. However, I still don't think dirty flashing the factory image is going to fix it, hopefully it does, but essentially your not removing the files that's causing the ui to fail. But we shall see.

 

[Mr. Blanco]

Dude, there's nothing to be embarrassed about, most of us have been there, no big deal. However, I still don't think dirty flashing the factory image is going to fix it, hopefully it does, but essentially your not removing the files that's causing the ui to fail. But we shall see.

well phone is back up and running completely stock now just about to flash twrp, and the flash kernal and magisk ...still not sure what caused this whole thing as i only installed flux substratum theme , phone was fine and fully functioning since last update ... and by the way thank you for reaching out to help me , i really appreciate it ....one thing that was strange though was when process what finished flashing , i got the corrupt device message warning before booting in to the os but everything seems fine so far

 

[Badger50]

well phone is back up and running completely stock now just about to flash twrp, and the flash kernal and magisk ...still not sure what caused this whole thing as i only installed flux substratum theme , phone was fine and fully functioning since last update ... and by the way thank you for reaching out to help me , i really appreciate it ....one thing that was strange though was when process what finished flashing , i got the corrupt device message warning before booting in to the os but everything seems fine so far

Glad your back up and running. Little FYI for you. Theme overlays can shut you down very quickly, as you now know. When twrp is working correctly, it's not as big deal, since you just go into twrp and flash the substratum rescue zip and all is well. So, going forward, if you want to theme, keep your lock screen security set to swipe or none until you are finished themeing. There is an adb way to push twrp to temporary cache so that you can use it. Here is the link if you want to learn how to do it ??

https://forum.xda-developers.com/pi...aimen-flash-kernel-1-00-t3702057/post75495348

 

[Mr. Blanco]

Glad your back up and running. Little FYI for you. Theme overlays can shut you down very quickly, as you now know. When twrp is working correctly, it's not as big deal, since you just go into twrp and flash the substratum rescue zip and all is well. So, going forward, if you want to theme, keep your lock screen security set to swipe or none until you are finished themeing. There is an adb way to push twrp to temporary cache so that you can use it. Here is the link if you want to learn how to do it

https://forum.xda-developers.com/pi...aimen-flash-kernel-1-00-t3702057/post75495348

Yes i will using your advice when attempting to theme or make any other adjustments from now on ...just found out i removed the -w from the factory image and not the one in the platforms tools so once again i have lost all saved data and starting from scratch..... grrrrrrr .... lol and thank you for the link ! i'm figuring since i'm starting from scratch that maybe i could check out the DU rom that's out right now , just wondering if you have flashed and if so how do you like it so far

 

[Badger50]

Yes i will using your advice when attempting to theme or make any other adjustments from now on ...just found out i removed the -w from the factory image and not the one in the platforms tools so once again i have lost all saved data and starting from scratch..... grrrrrrr .... lol and thank you for the link ! i'm figuring since i'm starting from scratch that maybe i could check out the DU rom that's out right now , just wondering if you have flashed and if so how do you like it so far

Oh yeah! I'm running it, and it's really solid! Bout the only thing not working is the squeeze thingy, which I never use anyway, and some issues with wifi calling. Other than that, it's great! ??

 

[Mr. Blanco]

Oh yeah! I'm running it, and it's really solid! Bout the only thing not working is the squeeze thingy, which I never use anyway, and some issues with wifi calling. Other than that, it's great!

That's awesome, glad to hear to that , and i can live with out squeeze and wifi calling i'm just about to give it a shot right now , wish me luck ..lol read your post on your/bajasur install instructions if it worked for you guys i'm hoping it will work for me ...... just to double check with you since you were able to get it up and running , is this the process ......
1. Be on February Security
2. Disable Security Pin in settings
3. Reboot to TWRP (Make backup if needed)
4. Factory Data Reset
5. Flash DU
6. Flash TWRP
7. Reboot ROM and set up without security
8. Reboot back to TWRP and flash latest Magisk
9. Reboot back to ROM and set up security
10. Done!

 

[Badger50]

That's awesome, glad to hear to that , and i can live with out squeeze and wifi calling i'm just about to give it a shot right now , wish me luck ..lol read your post on your/bajasur install instructions if it worked for you guys i'm hoping it will work for me ...... just to double check with you since you were able to get it up and running , is this the process ......
1. Be on February Security
2. Disable Security Pin in settings
3. Reboot to TWRP (Make backup if needed)
4. Factory Data Reset
5. Flash DU
6. Flash TWRP
7. Reboot ROM and set up without security
8. Reboot back to TWRP and flash latest Magisk
9. Reboot back to ROM and set up security
10. Done!

Yep, you got it. Justd don't wipe system in twrp! ?

 

[Mr. Blanco]

Yep, you got it. Justd don't wipe system in twrp!

just booted into twrp and don't have touch functions , as i'm completly stock now , should i flash the flash kernal to get touch functions in twrp and then follow that process

 

[Badger50]

just booted into twrp and don't have touch functions , as i'm completly stock now , should i flash the flash kernal to get touch functions in twrp and then follow that process

Did you disable lock screen security first? Kinda hard to flash a kernel if you don't have touch functions. Unless you adb push it.

 

[Mr. Blanco]

Did you disable lock screen security first? Kinda hard to flash a kernel if you don't have touch functions. Unless you adb push it.

Yes i disabled all security features ... lock screen / finger print but thinking i should have fastbooted twrp img and from with in the twrp img i should have flashed the Du rom zip and then the twrp zip ... is there a way to do the install with out touch functions like adb push ? never pushed anything to my device before and now wondering do i need to flash stock feb image again and then do the fastboot twrp img and from there flash the DU zip and then the permanent twrp zip ?

 

[Badger50]

Yes i disabled all security features ... lock screen / finger print but thinking i should have fastbooted twrp img and from with in the twrp img i should have flashed the Du rom zip and then the twrp zip ... is there a way to do the install with out touch functions like adb push ? never pushed anything to my device before and now wondering do i need to flash stock feb image again and then do the fastboot twrp img and from there flash the DU zip and then the permanent twrp zip ?

Try fastbooting the twrp.img first and see if you get it working fist :good:

 

[Mr. Blanco]

Try fastbooting the twrp.img first and see if you get it working fist :good:

Boom shaka laka ...... i got it up and running i fastbooted the stock boot.img and the did the twrp.img thing and flashed the rom and twrp and everything is up and running now, so glad it all worked out and , going to attemp to flash magisk now ... do you know if the latest magisk works 15.4 or should i stick with 15.3 ? and by the way thank you for helping with this whole process , i'm really grateful , big time props to you for all your help !!!!

 

[Badger50]

Boom shaka laka ...... i got it up and running i fastbooted the stock boot.img and the did the twrp.img thing and flashed the rom and twrp and everything is up and running now, so glad it all worked out and , going to attemp to flash magisk now ... do you know if the latest magisk works 15.4 or should i stick with 15.3 ? and by the way thank you for helping with this whole process , i'm really grateful , big time props to you for all your help !!!!

Saaweeeeeeeeeeet! Good job man :good: Magisk 15.4 is working fine for me. And, your very welcome ??

 

[Mr. Blanco]

Saaweeeeeeeeeeet! Good job man :good: Magisk 15.4 is working fine for me. And, your very welcome [/Q
i have a question , i got a message about a vendor image on my fist boot up , was just wondering if you did too and if thats just part of the package deal when using this rom

 

[Badger50]

Saaweeeeeeeeeeet! Good job man :good: Magisk 15.4 is working fine for me. And, your very welcome [/Q
i have a question , i got a message about a vendor image on my fist boot up , was just wondering if you did too and if thats just part of the package deal when using this rom

Some have reported the same on other AOSP roms. A possible fix, though not always successful, is to fastboot the vendor.img to both slots. The message is harmless, and won't cause any damage to your OS. It's just annoying at boot up is all ?