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.
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
Weird screen behavior, it seem to me that it isn't a hardware fault, cause when plugging in a charger the phone is able to show the MI logo, but not the charging icon
The phone is able to boot and i can hear the phone locking and unlocking, can see that the screen is on because of the backlight, but there is no image, SO FRUSTRATING!!
If you have any idea of what's going on and can give me a tip, i would thank you so much, the phone has been on this state for a long time
Don't know how to upload videos, if you think that can help diagnose it i can upload it and share a link or something
Hugask said:
Weird screen behavior, it seem to me that it isn't a hardware fault, cause when plugging in a charger the phone is able to show the MI logo, but not the charging icon
The phone is able to boot and i can hear the phone locking and unlocking, can see that the screen is on because of the backlight, but there is no image, SO FRUSTRATING!!
If you have any idea of what's going on and can give me a tip, i would thank you so much, the phone has been on this state for a long time
Don't know how to upload videos, if you think that can help diagnose it i can upload it and share a link or something
Click to expand...
Click to collapse
What did you do before?
Did you flash something?
Is it device unlocked?
This happen also in fastboot/recovery mode?
SubwayChamp said:
What did you do before?
Did you flash something?
Is it device unlocked?
This happen also in fastboot/recovery mode?
Click to expand...
Click to collapse
I hadnt updated my Rom, Pixel experience, in a while, so i took the opportunity and flashed an (at the time) beta Pixel Experience Android 10, i reverted and everything was fine for about one day i think, then some artifacting wich would come and go until the display gived up completly (about an hour between the two)
Yes, it is unlocked, and when in fastboot/recovery the screen is lighted up but not showing anything
My guess is that i have a low level firmware issue, as i had problem with those before (was running a custom ROM from day 1, so i had to manually update firware to use newer versions of PE (still pie version) and almost bricked my device
Hugask said:
I hadnt updated my Rom, Pixel experience, in a while, so i took the opportunity and flashed an (at the time) beta Pixel Experience Android 10, i reverted and everything was fine for about one day i think, then some artifacting wich would come and go until the display gived up completly (about an hour between the two)
Yes, it is unlocked, and when in fastboot/recovery the screen is lighted up but not showing anything
My guess is that i have a low level firmware issue, as i had problem with those before (was running a custom ROM from day 1, so i had to manually update firware to use newer versions of PE (still pie version) and almost bricked my device
Click to expand...
Click to collapse
Then try the next:
- Flash a different vendor.
- Flash a different kernel.
- Revert to stock ROM, no need to lock or nothing, just flash first the recovery ROM but if it doesn't result then flash the fastboot ROM through EDL, so that you know you can boot to EDL mode without need to open the back cover, this will restore all the original images.
SubwayChamp said:
Then try the next:
- Flash a different vendor.
- Flash a different kernel.
- Revert to stock ROM, no need to lock or nothing, just flash first the recovery ROM but if it doesn't result then flash the fastboot ROM through EDL, so that you know you can boot to EDL mode without need to open the back cover, this will restore all the original images.
Click to expand...
Click to collapse
Ok, so... i think i have all the files, but i'm really lost, how am i supposed to flash the vendor, firmware and stock ROM via fastboot?
Also, i put the device in fastboot, so... thats a win i guess (screen working surprisingtly)
I'm just not finding how to do this, it's been a while that i havent messed with this side of android, if you could help me it would mean the world for me
Hugask said:
Ok, so... i think i have all the files, but i'm really lost, how am i supposed to flash the vendor, firmware and stock ROM via fastboot?
Also, i put the device in fastboot, so... thats a win i guess (screen working surprisingtly)
I'm just not finding how to do this, it's been a while that i havent messed with this side of android, if you could help me it would mean the world for me
Click to expand...
Click to collapse
You can flash some images invoking the right partition, I mean, you can flash vendor image onto the vendor partition using
Code:
fastboot flash vendor vendor.img
, and in case you need to flash all the ROM you should use MiFlash tool
SubwayChamp said:
You can flash some images invoking the right partition, I mean, you can flash vendor image onto the vendor partition using
Code:
fastboot flash vendor vendor.img
, and in case you need to flash all the ROM you should use MiFlash tool
Click to expand...
Click to collapse
Ok, so... i am NOT keeping up with what i need to do, i found a vendor update in a site but it is not an image, i am so confused, i don't how was i able to mess around with this i am basically a noob, i feel so dumb, this should have been so easy and here i am having trouble
If you could make a step by step instruction or send a link where i can get a vendor .img it would be perfect thanks in advance
Hugask said:
Ok, so... i am NOT keeping up with what i need to do, i found a vendor update in a site but it is not an image, i am so confused, i don't how was i able to mess around with this i am basically a noob, i feel so dumb, this should have been so easy and here i am having trouble
If you could make a step by step instruction or send a link where i can get a vendor .img it would be perfect thanks in advance
Click to expand...
Click to collapse
Ok, update what is the current status of your device, you said screen now displaying, Did you refer only to fastboot mode? Could you see the bunny in fastboot? But booted up on system screen is displaying nothing?
SubwayChamp said:
Ok, update what is the current status of your device, you said screen now displaying, Did you refer only to fastboot mode? Could you see the bunny in fastboot? But booted up on system screen is displaying nothing?
Click to expand...
Click to collapse
Yes, that is correct, i can see the fastboot screen 100%, no artifacts, just plain working, still no recovery (if i remember right i have orange fox) or ROM screen
Hugask said:
Yes, that is correct, i can see the fastboot screen 100%, no artifacts, just plain working, still no recovery (if i remember right i have orange fox) or ROM screen
Click to expand...
Click to collapse
And what do you want to do now? Did you unlock bootloader?
SubwayChamp said:
And what do you want to do now? Did you unlock bootloader?
Click to expand...
Click to collapse
I actually want to check that, i took the phone to a tecnitician and he may have locked the bootloader
I think the next step would be flashing the vendor, firmwares and stock rom again, right?
Hugask said:
I actually want to check that, i took the phone to a tecnitician and he may have locked the bootloader
I think the next step would be flashing the vendor, firmwares and stock rom again, right?
Click to expand...
Click to collapse
if your bootloader is locked, you can't flash through fastboot mode either vendor or stock ROM, you should need to use EDL method or you can re-unlock bootloader and this way will work. Anyway i don't understand what actually your issue is.
SubwayChamp said:
if your bootloader is locked, you can't flash through fastboot mode either vendor or stock ROM, you should need to use EDL method or you can re-unlock bootloader and this way will work. Anyway i don't understand what actually your issue is.
Click to expand...
Click to collapse
The issue is the display not working, and it's gotta be a firmware issue as it's on my desk right now showing a bunny, also i am not used to fastboot flash anything, i just was used to recoveries and what not
Just runned some code and it's locked, this is getting better and better oh boy
How am i gonna unlock this if i can't even unlock the phone? last time with screen working it was already a nightmare, having to wait for miui account, do i have any method of doing this without using EDL?
Hugask said:
The issue is the display not working, and it's gotta be a firmware issue as it's on my desk right now showing a bunny, also i am not used to fastboot flash anything, i just was used to recoveries and what not
Just runned some code and it's locked, this is getting better and better oh boy
How am i gonna unlock this if i can't even unlock the phone? last time with screen working it was already a nightmare, having to wait for miui account, do i have any method of doing this without using EDL?
Click to expand...
Click to collapse
Well, this make sense although it's not clear if you did unlock it previously and after that at some time you did lock it again.
If you didn't unlock it previously you would need to bind your Mi account to the device and enable USB debugging and OEM unlock options but if you didn't before without a screen working you have a more difficult way, confirm me if that is the case.
Anyway I got happily surprised when I bought this device some months ago at the first attempt I could unlock it without have to wait time, try it and see what happen.
SubwayChamp said:
Well, this make sense although it's not clear if you did unlock it previously and after that at some time you did lock it again.
If you didn't unlock it previously you would need to bind your Mi account to the device and enable USB debugging and OEM unlock options but if you didn't before without a screen working you have a more difficult way, confirm me if that is the case.
Anyway I got happily surprised when I bought this device some months ago at the first attempt I could unlock it without have to wait time, try it and see what happen.
Click to expand...
Click to collapse
It was unloked and i locked again, don't know if this helps my case or if i am royally screwed up
And yeah, Xioami does make difficult to do the process of unlocking but only to recently released devices, aparently to stop re-sellers to buy the cheaper chinese rom and put the global version on them, i think that when a device doenst get made anymore makes sense that they would make it more easy (i bought the device 2 weeks after launch)
Hugask said:
It was unloked and i locked again, don't know if this helps my case or if i am royally screwed up
And yeah, Xioami does make difficult to do the process of unlocking but only to recently released devices, aparently to stop re-sellers to buy the cheaper chinese rom and put the global version on them, i think that when a device doenst get made anymore makes sense that they would make it more easy (i bought the device 2 weeks after launch)
Click to expand...
Click to collapse
Ok, of course this makes a huge difference, if you did unlock it previously then you couldn't receive any wait time, I wonder why you didn't try it if you didn 't. Check if MiUnlock tool unlock your device instantly.
SubwayChamp said:
Ok, of course this makes a huge difference, if you did unlock it previously then you couldn't receive any wait time, I wonder why you didn't try it if you didn 't. Check if MiUnlock tool unlock your device instantly.
Click to expand...
Click to collapse
OMG THIS WORKED
It's been sucessfully unlocked
Hugask said:
OMG THIS WORKED
It's been sucessfully unlocked
Click to expand...
Click to collapse
Hmm, OK, now you have your way sorted out, you can try with a custom ROM (all of them contain a vendor) or in case a custom ROM doesn't solve it you have to try a stock ROM through Mi Flash tool.
SubwayChamp said:
Hmm, OK, now you have your way sorted out, you can try with a custom ROM (all of them contain a vendor) or in case a custom ROM doesn't solve it you have to try a stock ROM through Mi Flash tool.
Click to expand...
Click to collapse
Ok, but how am i gonna flash a rom with fastboot? Is that a thing?
Also, i don't think the vendor is gonna be my only problem, but also the firmware, is there a way to flash firmware without the recovery and trough fastboot?
Hugask said:
Ok, but how am i gonna flash a rom with fastboot? Is that a thing?
Also, i don't think the vendor is gonna be my only problem, but also the firmware, is there a way to flash firmware without the recovery and trough fastboot?
Click to expand...
Click to collapse
You can't be sure of that, sometimes the vendor correct the issue, sometimes the firmware.
Firmware it is in the stock ROM that can be flashed either through fastboot or EDL mode (be careful to not relock bootloader or you couldn't enable this time OEM unlock option). Now that you have the way more clear just do a search "how to flash stock ROM on Xiaomi devices either through fastboot or EDL mode", just keep in mind that you don't need to open the back cover of the device, usually from a device off (only on unlocked ones) you could send it to EDL by pressing both volume buttons at same time that it is connected to PC, I gave you the main tips, for the rest you will find a lot of tutorials.
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.
The last time I rooted a phone was 3 years ago, in general whenever I try to root a phone I feel like the entire process has changed and im completely out of the loop.
All i want to do is make it so i can install f.lux and youtube vanced, how do I do this?
I know that I need to install magisk but apparently I also need to enable the bootloader whatever that means?
Sideload, flashing, caprip, boot-image, fastboot, TWRP: these words mean nothing to me, they serve to confuse and demean me.
Is there any resource for figuring out how to go from a new out-of-the-box moto g30 to one which lets me install youtube vanced? Usually I'd look up a tutorial but the only one I found was in spanish and I don't speak spanish.
Thanks for any help you can give.
First things first.
Android has Night Light built in and Youtube Vanced doesn't need root.
But, if you're still serious about rooting and installing magisk to make use of all of the really useful modules, you'll need:
An Unlocked Bootloader: Motorola's Own Guide
Keep in mind that unlocking the bootloader will wipe your phone and void its warranty, so be absolutely sure you want to do it and back up your files.
Then you'll need to manually patch a boot.img from your stock ROM (can be found here.) and flash it using ADB (Android Debug Bridge) using your PC.
I rooted mine within 3 days of owning it and have been enjoying it with no problems whatsoever ever since.
I used this guide as reference. If you have any questions you can always just message me here or on Telegram (@Kuntitled).
samjoebobtomted said:
The last time I rooted a phone was 3 years ago, in general whenever I try to root a phone I feel like the entire process has changed and im completely out of the loop.
All i want to do is make it so i can install f.lux and youtube vanced, how do I do this?
I know that I need to install magisk but apparently I also need to enable the bootloader whatever that means?
Click to expand...
Click to collapse
Bootloader is small program which runs before Android operating system running. Bootloader is first program to run so It is specific for board and processor. -RootJunky
Click to expand...
Click to collapse
Unlocking the bootloader
You can flash a custom system only if the bootloader allows it. Note, though, that the bootloader is locked by default. You can unlock the bootloader, but doing so deletes user data for privacy reasons. After unlocking, all data on the device is erased, that is, both private app data and shared data accessible over USB (including photos and movies). Before attempting to unlock the bootloader, back up any important files on the device. - https://source.android.com/setup/build/running
Click to expand...
Click to collapse
samjoebobtomted said:
Sideload,
Click to expand...
Click to collapse
Generally sideload means installing an app without the playstore.
samjoebobtomted said:
flashing,
Click to expand...
Click to collapse
Flashing usually refers to installing through fastboot mode or recovery
samjoebobtomted said:
caprip,
Click to expand...
Click to collapse
codename or development name for Moto G30
samjoebobtomted said:
boot-image
Click to expand...
Click to collapse
The boot.img is the fie that creates the boot partition
/bootThis is the boot partition of your Android device, as the name suggests. It includes the android kernel and the ramdisk. The device will not boot without this partition. Wiping this partition from recovery should only be done if absolutely required and once done, the device must NOT be rebooted before installing a new one, which can be done by installing a ROM that includes a /boot partition.
-RootJunky
Click to expand...
Click to collapse
samjoebobtomted said:
fastboot,
Click to expand...
Click to collapse
Fastboot refers to several things
Fastboot is the fastboot protocol to communicate with an Android device.
Fastboot.exe is the part of SDK Platform-Tools used to communicate with an Android device when it's in fastboot mode.
samjoebobtomted said:
TWRP:
Click to expand...
Click to collapse
Twrp is a Custom recovery,
The stock recovery has very limited functions,
a custom recovery has more options
/recoveryThis is specially designed for backup. The recovery partition can be considered as an alternative boot partition, that lets the device boot into a recovery console for performing advanced recovery and maintenance operations on it. -RootJunky
Click to expand...
Click to collapse
samjoebobtomted said:
these words mean nothing to me, they serve to confuse and demean me.
Is there any resource for figuring out how to go from a new out-of-the-box moto g30 to one which lets me install youtube vanced? Usually I'd look up a tutorial but the only one I found was in spanish and I don't speak spanish.
Thanks for any help you can give.
Click to expand...
Click to collapse
I have general Moto rooting instructions here
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Kuntitled said:
First things first.
Android has Night Light built in and Youtube Vanced doesn't need root.
Click to expand...
Click to collapse
Wait really I didn't even realize I didn't need a root for that lol.
Kuntitled said:
But, if you're still serious about rooting and installing magisk to make use of all of the really useful modules, you'll need:
An Unlocked Bootloader: Motorola's Own Guide
Keep in mind that unlocking the bootloader will wipe your phone and void its warranty, so be absolutely sure you want to do it and back up your files.
Then you'll need to manually patch a boot.img from your stock ROM (can be found here.) and flash it using ADB (Android Debug Bridge) using your PC.
I rooted mine within 3 days of owning it and have been enjoying it with no problems whatsoever ever since.
I used this guide as reference. If you have any questions you can always just message me here or on Telegram (@Kuntitled).
Click to expand...
Click to collapse
Hi thanks this really helped me get the grip of things haha.
I managed to unlock the bootloader but I'm a bit confused on what stock ROM you were referring to, the link you sent had a bunch of possibilities, I assume I need a reteu one since that's the name of my phone's software channel but there's a wide variety of them and the guide you sent seems to have their own ROM as well.
Either way thanks for all the help!
samjoebobtomted said:
Wait really I didn't even realize I didn't need a root for that lol.
Hi thanks this really helped me get the grip of things haha.
I managed to unlock the bootloader but I'm a bit confused on what stock ROM you were referring to, the link you sent had a bunch of possibilities, I assume I need a reteu one since that's the name of my phone's software channel but there's a wide variety of them and the guide you sent seems to have their own ROM as well.
Either way thanks for all the help!
Click to expand...
Click to collapse
You should check the Build Number under "About Phone" in settings, and match it what you find on that link i sent.
Wanted to find out if there was a way to revert to the stock rom without hassle.
Yeah, you can use LMSA for that.
arsradu said:
Yeah, you can use LMSA for that.
Click to expand...
Click to collapse
will it lock my bootloader though? Also did you face any issues while using that
rowhen_ said:
will it lock my bootloader though? Also did you face any issues while using that
Click to expand...
Click to collapse
No. And no.
Just make sure your power is stable, so it doesn't interrupt the flashing process.
Also, if you're doing that, I'm curious whether or not your OEM Unlocking option is still ON after flashing stock ROM. It should be ON. If it's not, don't attempt to lock back the bootloader or you may end up in a brick.
arsradu said:
No. And no.
Just make sure your power is stable, so it doesn't interrupt the flashing process.
Also, if you're doing that, I'm curious whether or not your OEM Unlocking option is still ON after flashing stock ROM. It should be ON. If it's not, don't attempt to lock back the bootloader or you may end up in a brick.
Click to expand...
Click to collapse
yeah, it's turned on by default
rowhen_ said:
yeah, it's turned on by default
Click to expand...
Click to collapse
Is it still on after flashing back stock ROM?
Cause, in my case, it's not. It's greyed out, and turned OFF. And it's driving me crazy, cause I don't know why is it still OFF.
arsradu said:
Is it still on after flashing back stock ROM?
Cause, in my case, it's not. It's greyed out, and turned OFF. And it's driving me crazy, cause I don't know why is it still OFF.
Click to expand...
Click to collapse
i havent flashed the stock rom yet so cant say, would it pose an issue if the OEM unlocking button is greyed out?
rowhen_ said:
i havent flashed the stock rom yet so cant say, would it pose an issue if the OEM unlocking button is greyed out?
Click to expand...
Click to collapse
No, but it would pose an issue if it's OFF and you want to relock the bootloader. Don't even attempt relocking your bootloader if that option is OFF.
That option can be:
1. active (not greyed out) with toggle ON or OFF.
2. inactive (greyed out) with toggle ON or OFF.
What's important is the position of that toggle. Because, what that says is that the bootloader is still unlockable.
YES, it is unlocked right now. And you might even get a message telling you that, but if the toggle is OFF, that means the bootloader is no longer unlockable (or get_unlock_ability=0).
Why is this bad? Well, because if you want to relock the bootloader, and something goes wrong, and you end up in an unbootable situation (with an error like "no valid operating system could be found"), you won't be able to unlock the bootloader again to fix your issue, or at least flash another ROM or something so you can boot back into the OS.
Fastboot will complain that the OEM Unlocking option is OFF, and will not allow you to flash anything. And obviously, you won't be able to boot back into the OS to turn it on.
So, be very careful about that option!
If you don't plan on relocking the bootloader, no worries. But if you do, be very, very careful what does that option say.
You can read more about it here.
arsradu said:
No, but it would pose an issue if it's OFF and you want to relock the bootloader. Don't even attempt relocking your bootloader if that option is OFF.
That option can be:
1. active (not greyed out) with toggle ON or OFF.
2. inactive (greyed out) with toggle ON or OFF.
What's important is the position of that toggle. Because, what that says is that the bootloader is still unlockable.
YES, it is unlocked right now. And you might even get a message telling you that, but if the toggle is OFF, that means the bootloader is no longer unlockable (or get_unlock_ability=0).
Why is this bad? Well, because if you want to relock the bootloader, and something goes wrong, and you end up in an unbootable situation (with an error like "no valid operating system could be found"), you won't be able to unlock the bootloader again to fix your issue, or at least flash another ROM or something so you can boot back into the OS.
Fastboot will complain that the OEM Unlocking option is OFF, and will not allow you to flash anything. And obviously, you won't be able to boot back into the OS to turn it on.
So, be very careful about that option!
If you don't plan on relocking the bootloader, no worries. But if you do, be very, very careful what does that option say.
You can read more about it here.
Click to expand...
Click to collapse
That makes sense. Yeah I dont mind the unlocked bootloader, no plans on relocking it.
Also The LMSA doesnt seem to detect my phone, is there like a guide I that I can follow to flash the stock ROM? (I'm currently on PE 12 )
rowhen_ said:
That makes sense. Yeah I dont mind the unlocked bootloader, no plans on relocking it.
Also The LMSA doesnt seem to detect my phone, is there like a guide I that I can follow to flash the stock ROM? (I'm currently on PE 12 )
Click to expand...
Click to collapse
You don't really need a guide. But yeah, LMSA won't detect the phone anymore because of the custom ROM.
You need the Rescue option and you need to enter your IMEI for the device to be detected. Everything else is self explanatory. The device needs to be in fastboot mode for this procedure. And make sure the cable is ok. I would recommend using the original cable.
arsradu said:
You don't really need a guide. But yeah, LMSA won't detect the phone anymore because of the custom ROM.
You need the Rescue option and you need to enter your IMEI for the device to be detected. Everything else is self explanatory. The device needs to be in fastboot mode for this procedure. And make sure the cable is ok. I would recommend using the original cable.
Click to expand...
Click to collapse
I flashed the stock rom and yes, the bootloader option is greyed out but unlocked. But tbh the rom's pretty trash lol. This was the reason I started considering custom rom's in the first place.
rowhen_ said:
I flashed the stock rom and yes, the bootloader option is greyed out but unlocked. But tbh the rom's pretty trash lol. This was the reason I started considering custom rom's in the first place.
Click to expand...
Click to collapse
So the OEM Unlocking option is ON in your case? Could you please help me with a screenshot, for reference? I'm trying to understand why mine is OFF.
Also, which custom ROM did you have before going back to stock ROM?
arsradu said:
So the OEM Unlocking option is ON in your case? Could you please help me with a screenshot, for reference? I'm trying to understand why mine is OFF.
Also, which custom ROM did you have before going back to stock ROM?
Click to expand...
Click to collapse
No Its turned off but greyed out. And the subtext below it says "bootloader already unlocked". Sorry cant share screenshots because I've already switched to lineage os 20. The stock rom was almost unusable
rowhen_ said:
No Its turned off but greyed out. And the subtext below it says "bootloader already unlocked". Sorry cant share screenshots because I've already switched to lineage os 20. The stock rom was almost unusable
Click to expand...
Click to collapse
Ah ok. But why do you say it was almost unusable? I didn’t have any issues with it? Also, in the meantime, I’ve relocked my bootloader, and thank Goodness, everything went fine.
What do you like in LineageOS? Personally I don’t like it.
arsradu said:
Ah ok. But why do you say it was almost unusable? I didn’t have any issues with it? Also, in the meantime, I’ve relocked my bootloader, and thank Goodness, everything went fine.
What do you like in LineageOS? Personally I don’t like it.
Click to expand...
Click to collapse
It was stuttering like crazy, the battery life was surprisingly trash. I prefer Pixel Experience 13 over Lineage OS but I was facing some minor issues with it so stuck with Lineage
rowhen_ said:
It was stuttering like crazy, the battery life was surprisingly trash. I prefer Pixel Experience 13 over Lineage OS but I was facing some minor issues with it so stuck with Lineage
Click to expand...
Click to collapse
That's weird... I've got no stuttering, battery is pretty damn good, so is signal, and I've got IMS services, which are pretty important to me. Also, Tap to Pay now works again, after locking the bootloader.
Well, I'm glad Lineage works for your! I also prefer PE. But...there are some issue right now. And I'm waiting for a new update which could potentially fix them.