Hey idk if it's just me. Cause I was late finding out bout the android 12 beta. And I failed to read everything. So I got the tmo converted to eu. So ya needless to say bootlooped. But I noticed in developers options dsu had both slots filled and it actually worked I can go back and forth to android gms gsi. Or just pure asop. So check see if anyone else has that working?
I'm sorry can you explain little more, the beta loaded DSU with both asop and android gms images?
Ya it did. I didn't know at the time I posted this that the gsi was out also. It was the first time I seen dsu working. I have been following treble since day one. I am glad google did not scrap it. Just got excited when I posted that.
amaroney55 said:
Ya it did. I didn't know at the time I posted this that the gsi was out also. It was the first time I seen dsu working. I have been following treble since day one. I am glad google did not scrap it. Just got excited when I posted that.
Click to expand...
Click to collapse
I see the two options in my developer settings. How does it work exactly? Will being rooted cause any problem loading it? Does it only stay loaded only until next reboot?
Shooter7889 said:
I see the two options in my developer settings. How does it work exactly? Will being rooted cause any problem loading it? Does it only stay loaded only until next reboot?
Click to expand...
Click to collapse
I get an error message when selecting
Oh. I haven't tried clicking on either. I'll try
When I clicked on one w/gms it asked for my fingerprint then started downloading. I cancelled it (untill I find out if it is just for one boot or if it cld wipe my phone or what have you)
I wouldn't bt
It doesn't. Will just flip over the beta the gms is with google other is pure android when you get ready to go back to stock or whatever your using look in the notifications.
amaroney55 said:
It doesn't. Will just flip over the beta the gms is with google other is pure android when you get ready to go back to stock or whatever your using look in the notifications.
Click to expand...
Click to collapse
Cool thanks I'll check it out
Your bootloader has to be unlocked tho.
amaroney55 said:
Your bootloader has to be unlocked tho.
Click to expand...
Click to collapse
I'm unlocked and rooted..le2125 on EU rom
amaroney55 said:
Your bootloader has to be unlocked tho.
Click to expand...
Click to collapse
I'm unlocked and rooted..le2125 on EU rom
Says it is working on mine , but it just boots to an un-setup OnePlus Android OOS 11...US Unlocked.
I tried it too then someone on telegram tols me that dsu on oneplus phones used vendor of oos 11.but i saw a video guide of someone that has the nord and he used the dsu method and he got android 12 gsi..strange thing
Ya see that is what I am not understanding. Treble was only to change the system.img. and nothing else. Then they started messing with the vendor and that defeated the purpose of a generic img. To me if your going to change the system and vendor and recovery might as well be OEM only. But I didn't have a problem with it on oneplus 9 pro using 11. But my oneplus 7 pro it will install it but will not boot to it. Using 10 or 11.
Oh I am using a tmo converted to eu.
Related
so hey guys, i think i kinda screwed up.
I wanted to install remix os on my Pixel C.
I followed the guide on here: http://forum.xda-developers.com/pixel-c/general/guide-unlock-bootloader-install-custom-t3307183
But i got in some problems, at installing the exceed kernell
now, after this i followed the official Remix OS install guide and Remix OS installed succesfully.
But my bootloader is still unlocked and i have no idea if my custom recovery is working.
How do i fix this? I hope you guys can help
@VillyLane
You will always get this boot screen, as long as your bootloader is unlocked.
cam30era said:
@VillyLane
You will always get this boot screen, as long as your bootloader is unlocked.
Click to expand...
Click to collapse
Can i lock it again?
VillyLane said:
Can i lock it again?
Click to expand...
Click to collapse
yeah you can but wouldn't recommend it if you ain't running stock
Simonthow said:
yeah you can but wouldn't recommend it if you ain't running stock
Click to expand...
Click to collapse
And is there a way that i still can root Remix OS
VillyLane said:
And is there a way that i still can root Remix OS
Click to expand...
Click to collapse
Yeah if you haven't locked the bootloader and take a look at this thread http://forum.xda-developers.com/pixel-c/general/discussion-remix-os-3-0-pixel-c-t3431368
Just unlocked a new Pixel c and getting that
Bootloader is unlocked and OS verification is OFF. Device will continue booting in 30 secs Message
Wondering still no way around that ?
Never seen it before don't see it on my Nexus 6 is it something specific to the Pixel ?
Markeee said:
Just unlocked a new Pixel c and getting that
Bootloader is unlocked and OS verification is OFF. Device will continue booting in 30 secs Message
Wondering still no way around that ?
Never seen it before don't see it on my Nexus 6 is it something specific to the Pixel ?
Click to expand...
Click to collapse
Yes it's on Pixel C only no way around it unless you stay 100% stock locked
Let me get my head on straight understanding a few facts
I understand that every-time you unlock the boot loader it wipes your installed apps
But once your rooted can you re lock and stay rooted ?
Please delete, creating new thread
Took an OTA and now whenever I turn the device on it says in red letters: "Your device is corrupt. It can't be trusted and may not work properly". I can still boot into the OS normally. I can still access fastboot. I can still access recovery. I have done many searches and people keep saying to relock the bootloader or unlock the bootloader and flash stock firmware. There's no way to do either because this Verizon variant is locked down like Fort Knox. I don't understand why the bootloader has to be unlocked to flash STOCK firmware straight from Verizon. Smh. Anyways, does anyone have any ideas. about how to get rid of this message?
ClassickWORLD said:
Took an OTA and now whenever I turn the device on it says in red letters: "Your device is corrupt. It can't be trusted and may not work properly". I can still boot into the OS normally. I can still access fastboot. I can still access recovery. I have done many searches and people keep saying to relock the bootloader or unlock the bootloader and flash stock firmware. There's no way to do either because this Verizon variant is locked down like Fort Knox. I don't understand why the bootloader has to be unlocked to flash STOCK firmware straight from Verizon. Smh. Anyways, does anyone have any ideas. about how to get rid of this message?
Click to expand...
Click to collapse
You could side load the Google OTA image and see if that fixes it. Or just wait until next week and see if the March OTA fixes it. If your device is working properly, I wouldn't worry too much about it.
Badger50 said:
You could side load the Google OTA image and see if that fixes it. Or just wait until next week and see if the March OTA fixes it. If your device is working properly, I wouldn't worry too much about it.
Click to expand...
Click to collapse
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
ClassickWORLD said:
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
Click to expand...
Click to collapse
While I haven't done it personally, I've seen several people do just that from stock recovery. At worst, the install will fail and nothing will be changed. Unlocking the bootloader is mainly for flashing factory images and rooting, not OTA's. Just follow the instructions from Google and see what happens. In your current situation, you really have nothing to lose.
https://developers.google.com/android/ota
ClassickWORLD said:
I have moved on to the iPhone 8 Plus. I sold the device and had it returned because of that message... and now I want to sell it again. I just need to get rid of it. So you are saying that I can sideload via adb even on a Verizon device with a locked bootloader?
Click to expand...
Click to collapse
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
michaelbsheldon said:
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
Click to expand...
Click to collapse
Thanks for the conformation my friend. I kinda feel sorry for that poor guy, he went to an iphone!!.....oh the horror! ??????
michaelbsheldon said:
Yes, I have a Verizon version of the Pix2-XL, and I have run 4 or 5 times on it.
https://developers.google.com/android/ota
Use these instructions exactly, and be sure you have the newest Android Tools.
This should take care of your error message.
Click to expand...
Click to collapse
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
ClassickWORLD said:
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
Click to expand...
Click to collapse
Huh?? You have a P2XL right?? It's right there at the bottom of the P2XL section.
What build month are you currently on?
ClassickWORLD said:
Hey thanks for that. The latest image I see for the Verizon Pixel XL 2 is for 8.0.0 from Nov 2017. I am on 8.1. So I have to downgrade? Is that even possible?
Click to expand...
Click to collapse
You do want the February one. It's for all phones including Verizon.
Badger50 said:
Huh?? You have a P2XL right?? It's right there at the bottom of the P2XL section.
What build month are you currently on?
Click to expand...
Click to collapse
So I can flash that with no radio issues? I thought OPM1 is google, OPM2 is Telus only, and OPD3 is Verizon only? I have a Verizon P2XL
Edit: I think I've found my issue. The person who had the device before me must have sideloaded 8.1.0 (OPM1.171019.018, Feb 2018)" to this device and that may be the reason for the error. I am thinking because that's not the Verizon P2XL firmware but the Google P2XL device firmware.
michaelbsheldon said:
You do want the February one. It's for all phones including Verizon.
Click to expand...
Click to collapse
Ok gotcha. Downloading now as we speak.
Badger50 said:
Thanks for the conformation my friend. I kinda feel sorry for that poor guy, he went to an iphone!!.....oh the horror! ??
Click to expand...
Click to collapse
Lol I still have my trusty ol' Nexus 6P as my secondary device.
WoW this download link is really slow. Downloading at 50 KB/s. Says 9 hours left. I have fiber speeds for my internet. Anyone know of any alternative download locations for this OTA?
Edit: Rebooted my router and that fixed it. It downloaded in 2 minutes.
ClassickWORLD said:
WoW this download link is really slow. Downloading at 50 KB/s. Says 9 hours left. I have fiber speeds for my internet. Anyone know of any alternative download locations for this OTA?
Edit: Rebooted my router and that fixed it. It downloaded in 2 minutes.
Click to expand...
Click to collapse
Fixed and you're a happy camper, right?
P.S. try a factory reset to complete this
You guys are great. The sideload fixed the problem! I truly appreciate you guys. Thanks a lot.
ClassickWORLD said:
Lol I still have my trusty ol' Nexus 6P as my secondary device.
Click to expand...
Click to collapse
Ok bruh, your forgiven :laugh: Did you get your problem fixed?
Oooops....never mind. I see that you did :good:
Is this the method for unlocking a Verizon Pixel 2 XL? Or just to fix the message this person was receiving. I want to buy a verizon Pixel 2 XL today in the store and do this vs waiting on google to deliver it.
tradermatt said:
Is this the method for unlocking a Verizon Pixel 2 XL? Or just to fix the message this person was receiving. I want to buy a verizon Pixel 2 XL today in the store and do this vs waiting on google to deliver it.
Click to expand...
Click to collapse
There is no method to unlock the Verizon P2XL!!
Hi all,
Pixel 3 XL
Android 10(QP1A.190711.020)
ELEMENTALX-P3-2.05
Have a look at attached screenshots, how would one apply the new update without messing it up, i finally have GPay working, and I really want to keep it that way.
Thanks
I cant seem to be able to upload attachments, "url can not prase" ?
Not sure about keeping Google pay, but I followed A/B slot update from here https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
Everything is working fine on QP1A.190711.020.C3
You will need to reflash the kernel.
Only using systemless hosts and edge sense modules in magisk.
rob42ert said:
Hi all,
Pixel 3 XL
Android 10(QP1A.190711.020)
ELEMENTALX-P3-2.05
Have a look at attached screenshots, how would one apply the new update without messing it up, i finally have GPay working, and I really want to keep it that way.
Thanks
I cant seem to be able to upload attachments, "url can not prase"
Click to expand...
Click to collapse
How'd you get Google Pay working?
I flashed the complete system img removing the -w and re-rooted (pulled boot.img from the zip and had magisk patch it and flash in fastboot)
rquinn19 said:
How'd you get Google Pay working?
I flashed the complete system img removing the -w and re-rooted (pulled boot.img from the zip and had magisk patch it and flash in fastboot)
Click to expand...
Click to collapse
Gpay i got it working with BostonDan method.
Can you please link Boston Dan method?
skaforey said:
Can you please link Boston Dan method?
Click to expand...
Click to collapse
pretty easy to google BostonDan and Google Pay. First result. https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
Edit: Just tried it on my rooted Android 10 3XL and I was able to add my cards. Haven't used it yet but generally if I can add cards I can use it. Thanks
henderjr said:
pretty easy to google BostonDan and Google Pay. First result. https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
Edit: Just tried it on my rooted Android 10 3XL and I was able to add my cards. Haven't used it yet but generally if I can add cards I can use it. Thanks
Click to expand...
Click to collapse
I have been using that method since the day he posted it on a 3 and 3 XL. Both are on 10, and got clean wiped to do so. Both had card reinstalled and have been used at the terminal since the c3 update.
sliding_billy said:
I have been using that method since the day he posted it on a 3 and 3 XL. Both are on 10, and got clean wiped to do so. Both had card reinstalled and have been used at the terminal since the c3 update.
Click to expand...
Click to collapse
Good to hear.! I have a WearOS watch with Google Pay so I haven't had a need to use my phone much.
I have to get rid of ElementalX without losing all my stuff. This kernel has many bugs, my assistent won't start when squeezed anymore.
Is there a way?
rob42ert said:
I have to get rid of ElementalX without losing all my stuff. This kernel has many bugs, my assistent won't start when squeezed anymore.
Is there a way?
Click to expand...
Click to collapse
How exactly have you determined that it is the kernel, and what does "many bug" mean? There are a lot of us who are using ElementalX on 10 with no issues including assistant squeeze. You can start by installing any other kernel available in the "Google Pixel 3 XL ROMs, Kernels, Recoveries, & Other Development" section (you will need to re-root) and see if it makes any difference. It would also be a good idea if you posted in the dedicated thread for ElementalX. Besides getting user answers, @flar2 will be able to answer any questions specific since it is his kernel.
As for possible issues, how you installed could (dirty, clean, OTA/OTA sideload, factory image in BL) make a very possible difference as well as what version you have installed (specifically if you installed the new c3 image). It sounds like you have a bad Android 10 install and are going to end up needing a full clean install. Good luck.
rob42ert said:
I have to get rid of ElementalX without losing all my stuff. This kernel has many bugs, my assistent won't start when squeezed anymore.
Is there a way?
Click to expand...
Click to collapse
There are no bugs in ElementalX kernel.
Hello,
I have a device that I obtained through beta testing that has not been released yet. I am allowed to keep the device now that testing is over. I am not happy with the stock rom and some of the apps it forces you to keep. I cannot remove them through ABD either. There is no stock ROM image available yet. Therefore, I cannot port TWRp or root.
I stumbled on project treble. I ran treble check and it says my phone is supported as it came with android 11. It supports systemless updates and has A/B system partition. I really like stock android ASOP. Is there anyway I can flash a generic image? What's the odds of it working correctly? Since there is no image available yet and I cannot port TWRP I have to worrying about not being able to recover the device if things go wrong. I know you can flash without TWRP which is why I decided to ask about this. Would I have a better chance flashing roms for supported devices with similar hardware? How should I proceed?
Thanks,
Rocky
as long as you have a compatible custom recovery AND the stock rom in case something go wrong, you can flash any GSI according to your device's architecture
Roizoulou said:
as long as you have a compatible custom recovery AND the stock rom in case something go wrong, you can flash any GSI according to your device's architecture
Click to expand...
Click to collapse
Since it is a beta unit I have neither as it has not been officially released. I have never flashed one of these roms so I do not know how well they work after flashing. I know the device has a pretty popular SOC which is a snapdragon 750g so I would assume if a gai runs good on another device using the 750g then it should work.
bigroc2223 said:
Since it is a beta unit I have neither as it has not been officially released. I have never flashed one of these roms so I do not know how well they work after flashing. I know the device has a pretty popular SOC which is a snapdragon 750g so I would assume if a gai runs good on another device using the 750g then it should work.
Click to expand...
Click to collapse
best you can do is dump the whole rom, make a backup before going any further
Roizoulou said:
best you can do is dump the whole rom, make a backup before going any further
Click to expand...
Click to collapse
I don't think I can dump it without root right?
bigroc2223 said:
I don't think I can dump it without root right?
Click to expand...
Click to collapse
an unlocked bootloader first and just search for how to dump system on google. it usually just need a pc and ADB
bigroc2223 said:
I don't think I can dump it without root right?
Click to expand...
Click to collapse
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
Roizoulou said:
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried this before it requires root. I just double checked and the prereqs say root required too. This sucks because the device has decent specs. It's just the ROM and software on it are crappy. After doing some reading the biggest thing I'm worried about is flashing and not having mobile data since it is a 5g phone. I read about someone else flashing and not being able to get their mobile data to work.
bigroc2223 said:
I tried this before it requires root. I just double checked and the prereqs say root required too. This sucks because the device has decent specs. It's just the ROM and software on it are crappy. After doing some reading the biggest thing I'm worried about is flashing and not having mobile data since it is a 5g phone. I read about someone else flashing and not being able to get their mobile data to work.
Click to expand...
Click to collapse
what is the device?
Roizoulou said:
what is the device?
Click to expand...
Click to collapse
It's a beta device from TCL. It has not been released yet. I read that phh GSI should be compatible with all android phones with treble support. Therefore, I think I might just go for it. The only thing is if I end up with a bug I more than likely will probably have to figure it out on my own.
bigroc2223 said:
It's a beta device from TCL. It has not been released yet. I read that phh GSI should be compatible with all android phones with treble support. Therefore, I think I might just go for it. The only thing is if I end up with a bug I more than likely will probably have to figure it out on my own.
Click to expand...
Click to collapse
just try phh's first and if you encounter issues, try other custom roms
Roizoulou said:
just try phh's first and if you encounter issues, try other custom roms
Click to expand...
Click to collapse
I think I might of found a solution. I am pretty sure there is a way to boot a ROM before flashing it. I could of sworn I read this somewhere. It was an adb command. It allowed you too boot the ROM instead of flashing it. This would allow me to preview the ROM before officially flashing it to the device. I just cannot remember where I saw this at or the command.
My goal is to get a working gsi installed. From there I would like to get TWRP flashed on the device so it can be rooted. If I would need to port TWRP I think I could figure it out. This way when the device is officially released it will have TWRP ready to go for it. Also, since it will have TWRP I will be able to start porting roms as soon as they release the system image.
bigroc2223 said:
I think I might of found a solution. I am pretty sure there is a way to boot a ROM before flashing it. I could of sworn I read this somewhere. It was an adb command. It allowed you too boot the ROM instead of flashing it. This would allow me to preview the ROM before officially flashing it to the device. I just cannot remember where I saw this at or the command.
My goal is to get a working gsi installed. From there I would like to get TWRP flashed on the device so it can be rooted. If I would need to port TWRP I think I could figure it out. This way when the device is officially released it will have TWRP ready to go for it. Also, since it will have TWRP I will be able to start porting roms as soon as they release the system image.
Click to expand...
Click to collapse
like DSU loader?
Roizoulou said:
like DSU loader?
Click to expand...
Click to collapse
Never heard of that this was just an adb command.
I just downloaded ASOP 11.0 v309. Treble info says my device requires system-arm64-ab.img.xz. So I downloaded system-roar-arm64-ab-gapps.img.xz and system-roar-arm64-ab-vanilla.ikg.gz so hopefully those are the right ones. One has Gapps and one does not. Was going to flash the Gapps version first and see how things go. Then if need be flash vanilla.
I got a problem with phone calls. When I dial out I get call ended. Incoming calls I can hear them ring but get no way to answer. Also I am not getting text messages.
Roizoulou said:
like DSU loader?
Click to expand...
Click to collapse
I got it all working bro thanks for your help
bigroc2223 said:
I got it all working bro thanks for your help
Click to expand...
Click to collapse
gapps or vanilla?
Roizoulou said:
gapps or vanilla?
Click to expand...
Click to collapse
I was able to get them both to work. However, I am trying to use the gapps version, but I am getting an error that the device is not google certified. I cannot find a workaround unless I unroot which I do not want to do =(
bigroc2223 said:
I was able to get them both to work. However, I am trying to use the gapps version, but I am getting an error that the device is not google certified. I cannot find a workaround unless I unroot which I do not want to do =(
Click to expand...
Click to collapse
rooted with magisk?
Roizoulou said:
rooted with magisk
Click to expand...
Click to collapse
It comes rooted with phh superuser. I'm trying to find a way to pull my boot.img from the device so I can use it to flash magisk since it has a workaround for non Google certified devices.
Guys, I have experienced and heard a lot from others that they come back to stock rom after enjoying the custom ROM for a week or two
just because they missed the OOS Stock cam application performance and features. And we all know, there isnt a custom ROM in which
OOS Cam works flawlessly. I might have a possible solution for this. To be frank, I havent tried this solution yet and I m no expert on
developing ROMS. This is just an idea. Therefore, to confirm this, I m putting forward my idea to the community.
Normally, GCAM works fine for me in Custom ROMS for taking few PICS here n there. But the problem arises when I goto a Vacation trip
or attend a party/function where Camera is an essential requirement. And GCAM just cant beat the shear video and photo performance
of stock OOS CAM. So, my solution might help guys in similar situations.
The possible solution maybe:-
1) Install an awesome Custom ROM of choice primarily on device.
2) Select DSU loader from the developer options
3) Choose the suitable Stock DSU Image. This will install the Stock ROM without affecting the primary custom ROM.
Just go thru normal step process and leave it at that. Remember we only need Stock OOS camera app from this ROM.
Therefore, during normal usage days. just use the CUstom ROM which doesnt require clicking videos or many photos.
However, during trips/vacations/functions, just quickly restart your device to switch to the DSU Image.
and voila, USE THE STOCK OOS CAM as usual and save all photos/videos.
Please let me know if this idea will work theoretically and practically?
I was actually wondering if dual boot was possible. I had no idea about DSU Loader before.
Is it possible to install OOS into the DSU Loader though? I did some quick research and it's meant for GSIs.
Would be cool if we had a tool like this that allowed OOS to be the secondary so we have a fully working custom ROM and OOS when needed.
I have tried dsu loader and it sent me to the your devuce is corrupt red screen.had to start from scratch.also the dsu loader will relock your bootloader.
gillim74 said:
I have tried dsu loader and it sent me to the your devuce is corrupt red screen.had to start from scratch.also the dsu loader will relock your bootloader.
Click to expand...
Click to collapse
lol, what? DSU doesn't lock your bootloader. Actually, in order to use DSU, your bootloader needs to be unlocked.
Please, double-check before spreading false information.
EtherealRemnant said:
I was actually wondering if dual boot was possible. I had no idea about DSU Loader before.
Is it possible to install OOS into the DSU Loader though? I did some quick research and it's meant for GSIs.
Would be cool if we had a tool like this that allowed OOS to be the secondary so we have a fully working custom ROM and OOS when needed.
Click to expand...
Click to collapse
I have seen that a custom DSU loader is also present which can easily install custom ROMS.
If we make OOS primary and custom ROM secondary and use that secondary ROM as primary. Wont that work?
i assume secondary DSU Custom ROMS dont have limited functionality.
sunny1689gupta said:
I have seen that a custom DSU loader is also present which can easily install custom ROMS.
If we make OOS primary and custom ROM secondary and use that secondary ROM as primary. Wont that work?
i assume secondary DSU Custom ROMS dont have limited functionality.
Click to expand...
Click to collapse
I was reading that calls don't work on the secondary ROM but maybe that was in that specific instance. I didn't spend a lot of time on reading.
The custom loader I saw seemed to only be for GSIs too which is why I asked if it can be used for regular ROMs.
Hmm.. nice point. Lets see if an expert can reply here
ekin_strops said:
lol, what? DSU doesn't lock your bootloader. Actually, in order to use DSU, your bootloader needs to be unlocked.
Please, double-check before spreading false information.
Click to expand...
Click to collapse
It did mine so i do know what i am talking about.i wouldnt post something i didnt experience personally.i did it both ways with it locked and unlocked and both times put me at the red your device is corrupt screen.
gillim74 said:
It did mine so i do know what i am talking about.i wouldnt post something i didnt experience personally.i did it both ways with it locked and unlocked and both times put me at the red your device is corrupt screen.
Click to expand...
Click to collapse
which option did u choose? Did u choose the right GSI DSU file. How much I know there are 4 to 5 options.
That could have been the issue choosing the wrong one.i didnt think they would give you the option to install one if it didnt work but that very well could have been the issue.i believe i chose the last option.
sunny1689gupta said:
which option did u choose? Did u choose the right GSI DSU file. How much I know there are 4 to 5 options.
Click to expand...
Click to collapse
gillim74 said:
It did mine so i do know what i am talking about.i wouldnt post something i didnt experience personally.i did it both ways with it locked and unlocked and both times put me at the red your device is corrupt screen.
Click to expand...
Click to collapse
You do know that that screen is always present when you have an unlocked bootloader, right? Lol
TheKnux said:
You do know that that screen is always present when you have an unlocked bootloader, right? Lol
Click to expand...
Click to collapse
Yes its not the yellow screen when you boot.it was a red screen that says your device is corrupt and cannot boot please visit the link from another device.
@gillim74 that's literally the screen I have every time I boot or restart my phone and it still successfully boots.
@sunny1689gupta could you PM if you don't mind? Either on here or telegram. Same username.
TheKnux said:
@gillim74 that's literally the screen I have every time I boot or restart my phone and it still successfully boots.
Click to expand...
Click to collapse
What os are you running
gillim74 said:
What os are you running
Click to expand...
Click to collapse
OOS.
TheKnux said:
OOS.
Click to expand...
Click to collapse
I think i have a messed up a slot.someone deleted the logical partition to try and flash a gsi and it dont flash roms right.i cant find a backup of one and ive done the whole msm thing.
gillim74 said:
I think i have a messed up a slot.someone deleted the logical partition to try and flash a gsi and it dont flash roms right.i cant find a backup of one and ive done the whole msm thing.
Click to expand...
Click to collapse
If you have a fully working slot with no issues, flash this via adb sideload or twrp. Just letting you know that the screen you're referring to is a known issue when having an unlocked bootloader when using OOS11 as a base. I DID NOT have this screen when running A12 Open Betas, even with an unlocked bootloader.
TheKnux said:
If you have a fully working slot with no issues, flash this via adb sideload or twrp. Just letting you know that the screen you're referring to is a known issue when having an unlocked bootloader when using OOS11 as a base. I DID NOT have this screen when running A12 Open Betas, even with an unlocked bootloader.
Click to expand...
Click to collapse
Cool thanks for the help and info
gillim74 said:
It did mine so i do know what i am talking about.i wouldnt post something i didnt experience personally.i did it both ways with it locked and unlocked and both times put me at the red your device is corrupt screen.
Click to expand...
Click to collapse
"It did mine, therefore it must be a fact that it's how it works". NO. Again, the DSU loader needs an unlocked bootloader. What happened or what it didn't happen to your device is irrelevant. It's a FACT that your DSU doesn't LOCK your bootloader because it would self-corrupt itself by doing that since the DSU needs an unlocked Bootloader.
Imagine developers making DSU that requires an unlocked bootloader, but in the process of flashing a GSI (Generic System Image), it will lock the bootloader by itself and brick itself. That absolutely makes no sense, and neither it is coded to work like that.