What happens if you flash GSI on unsupported device? - Treble-Enabled Device Questions and Answers

I have TWRP installed as my permanent recovery on my device. My question is what would happen if I flash (for example) system-arm64-aonly-gapps-su.img using TWRP on my device? Will it bricked? Can I restore it by flashing stock using ODIN?
I posted on a wrong thread. Kindly move it to https://forum.xda-developers.com/project-treble/trebleenabled-device-questions-and-answers since this is a question.

ECOTV said:
I have TWRP installed as my permanent recovery on my device. My question is what would happen if I flash (for example) system-arm64-aonly-gapps-su.img using TWRP on my device? Will it bricked? Can I restore it by flashing stock using ODIN?
I posted on a wrong thread. Kindly move it to https://forum.xda-developers.com/project-treble/trebleenabled-device-questions-and-answers since this is a question.
Click to expand...
Click to collapse
It won't brick, it just won't boot. The system image is designed to look for boot vendor etc in different partitions, not in the system as it previously was

miffymiffy said:
It won't brick, it just won't boot. The system image is designed to look for boot vendor etc in different partitions, not in the system as it previously was
Click to expand...
Click to collapse
So if I flash it and if it won't boot, can I return to stock using ODIN?

ECOTV said:
So if I flash it and if it won't boot, can I return to stock using ODIN?
Click to expand...
Click to collapse
No idea how you'd go back. The moral is don't flash it. It won't work

miffymiffy said:
It won't brick, it just won't boot. The system image is designed to look for boot vendor etc in different partitions, not in the system as it previously was
Click to expand...
Click to collapse
I have a Samsung Galaxy J4 Plus and it has treble support (A ONLY) but when i flash GSI it wont boot. it end up in a bootloop and i cant get it to boot. What should i do ??

dewin_prins said:
I have a Samsung Galaxy J4 Plus and it has treble support (A ONLY) but when i flash GSI it wont boot. it end up in a bootloop and i cant get it to boot. What should i do ??
Click to expand...
Click to collapse
Just wipe system and data and flash an specific rom for your device.

Schnedi said:
Just wipe system and data and flash an specific rom for your device.
Click to expand...
Click to collapse
i am at the boot screen of pixel experience gsi rom but it wont boot to system.. or it just takes a long time its been on the google logo for about an hour now and its not in the os yet should i wait or do something else i dont know what to do to make it go to the system..

Precautions for a gsi rom flash
If your device is supported then you must boot up with gsi
Do you wiped dalvik /cache / data partitions before booting with gsi or i say before flashing gsi rom

Related

Can't flash custom roms

Once again I am stuck in same situation.*
I can only boot on restored twrp backup.*
I cant boot on any other custom roms.*
It install perfectly but after i reboot it gets stuck on 1+ boot logo.*
op3lite
saultanised cm
cm14
be it any rom i am already on 3.2.7 firmware.*
Followed mega unbrick guide and restored stock partitions. the phone boots properly. but when i remove encryption via fastboot,phone doesnt boot after that. again i have to go through all unbrick guide. back to stock 3.1.2. none of the roms boot except twrp restore.*
I m totally fed up. Please help.
nikhilsnigam said:
Once again I am stuck in same situation.*
I can only boot on restored twrp backup.*
I cant boot on any other custom roms.*
It install perfectly but after i reboot it gets stuck on 1+ boot logo.*
op3lite
saultanised cm
cm14
be it any rom i am already on 3.2.7 firmware.*
Followed mega unbrick guide and restored stock partitions. the phone boots properly. but when i remove encryption via fastboot,phone doesnt boot after that. again i have to go through all unbrick guide. back to stock 3.1.2. none of the roms boot except twrp restore.*
I m totally fed up. Please help.
Click to expand...
Click to collapse
What twrp version are you using?
Piyush lalwani said:
What twrp version are you using?
Click to expand...
Click to collapse
latest official twrp
nikhilsnigam said:
latest official twrp
Click to expand...
Click to collapse
Can you give a try to nodded twrp and one more thing mount system before flashing any ROM.
Note: after decrypting if you want too boot into OOS you need to Flash SuperSU or otherwise the OOS will force encryption and that may create problem.
Piyush lalwani said:
Can you give a try to nodded twrp and one more thing mount system before flashing any ROM.
Note: after decrypting if you want too boot into OOS you need to Flash SuperSU or otherwise the OOS will force encryption and that may create problem.
Click to expand...
Click to collapse
I did that already. after flashing supersu immediately then also stuck at boot screen. tried with modded twrp too 3.0.2.22
Piyush lalwani said:
Can you give a try to nodded twrp and one more thing mount system before flashing any ROM.
Note: after decrypting if you want too boot into OOS you need to Flash SuperSU or otherwise the OOS will force encryption and that may create problem.
Click to expand...
Click to collapse
okay now after few trial and error method i have come to the conclusion that this happens only after unencrypting the device. after eunencrypting it wont boot any other roms except those which have been already backed up.
So,
can i flash roms on encrypted device? I mean i test a lot of roms and i change frequently.
I guess no, right?
Yes try with encryption as the ROMs doesn't require decrypting the device. Decrypted device is only required if you want to use multirom.
Good Luck.
Piyush lalwani said:
Yes try with encryption as the ROMs doesn't require decrypting the device. Decrypted device is only required if you want to use multirom.
Good Luck.
Click to expand...
Click to collapse
but every time we try to reboot in recovery it asks for password to decrypt.
and if i enter default password storage shows only 32gb. that is strange
nikhilsnigam said:
but every time we try to reboot in recovery it asks for password to decrypt.
and if i enter default password storage shows only 32gb. that is strange
Click to expand...
Click to collapse
In nodded recovery too?
Piyush lalwani said:
In nodded recovery too?
Click to expand...
Click to collapse
going to try with modded recovery this time
nikhilsnigam said:
going to try with modded recovery this time
Click to expand...
Click to collapse
Yeah give a try
Piyush lalwani said:
Yeah give a try
Click to expand...
Click to collapse
how does modded recovery helps in this btw?
hope it works
OK So I am able to flash any rom with encrypted storage and latest modified twrp.
This is working for me right now but still haven't found solution why it wouldn't work on unencrypted storage.
Thank you.
This guide solved everything
http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-decryption-ultimate-guide-t3497940

custom roms do not boot up

hi there,
i used crDroidAndroid-8.1-20180606-riva-v4.3 but there were color problems i didnt know 2 fix so i decided 2 flash a new rom resp. a newer version but no custom rom boots up.
when it tries 2 boot is freezes at the boot screen, then screen switches off and nothing happens. i can go 2 fastboot and recovery.
sometimes it boots up but after a few seconds it freezes 2.
i tried different roms and recoveries but nothing works.
i foolishly wiped internal storage once but then i flashed the stock rom again which boots up. then i unlocked the bootloader and flashed a custom recovery and a rom again but the same error is there (no booting up)
anyone got a solution for this problem? no unbricking suggestions plz
edit: im in the wrong thread i think. i wanted 2 post it in "Guides, News, & Discussion". cant delete it. sry for that
logs
so i managed 2 create logs while booting up.
1) https://pastebin.com/cgrX2DA1
2) https://pastebin.com/r7DmcN46
3) https://pastebin.com/0pwXyuys
4) https://pastebin.com/S41FG2SQ
1) is 1st part of the log while booting with no success to boot into the os.
2) is 2nd part of the log while booting with no success to boot into the os.
3) is 1st part of the log while booting with successful boot into the os.
4) is 2nd part of the log while booting with successful boot into the os.
i also tried 2 log "cat /proc/last_kmsg > /sdcard/last_kernel_message_log.txt"
and "dmesg > /sdcard/kernel_boot_log.txt" via terminal in linux but it only sais file or directory not found.
i hope sum1 can give me sum help now.
so i did this https://en.miui.com/thread-3921604-1-1.html but it doesnt help. as i expected.
any1? i can post more information if necessary. just say which and perhaps how ;D
cmon guys. i can impossibly b the only 1 who faces this problem.
i dont think its a hardware thing cause stock rom and android 7.1.2 (viper os) work. maybe a vendor problem? could flash another vendor img solve this problem? can sum1 send me his?
i got sum more logs after flashing rr 7.0:
logcat 1st part: https://pastebin.com/EBZAgbhF
logcat 2nd part: https://pastebin.com/qaMFrvxi
dmesg: https://pastebin.com/Gg8bYkJy
cheers
Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.
NaAnBcEhEuL9A8K7 said:
Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.
Click to expand...
Click to collapse
thx for ur answer but i tried this already. does not work on android 8 and 9 roms
daemonicvs said:
thx for ur answer but i tried this already. does not work on android 8 and 9 roms
Click to expand...
Click to collapse
Well it worked for me.
Which custom rom you want to use?
well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..
daemonicvs said:
well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..
Click to expand...
Click to collapse
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.
NaAnBcEhEuL9A8K7 said:
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.
Click to expand...
Click to collapse
i did it several times before but 2 b safe i did it again like that:
i flashed riva_global_images_V10.1.1.0.NCKMIFI_20181029.0000.00_7.1_global_f444c158ed.tgz using XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan-master. im on linux mint 18.3. i have 4 options:
flash_all_lock.sh
flash_all_lock_crc.sh
flash_all_except_data_storage.sh
flash_all.sh
i chose flash_all.sh
i booted into the stock rom and set it up, enabled dev options and adb.
then i switched it off, went into bootloader, flashed twrp-3.2.3-0-riva.img via fastboot.
after that i entered twrp, flashed OrangeFox-R8.3-riva.zip and rebooted into recovery
i wiped everything except external sd and usb otg (i dont have these)
after a reboot intorecovery i formatted data then rebooted in recovery
i flahed crDroidAndroid-9.0-20181002-riva-v5.0.zip
then reboot into system
no success as i expected! wtf is wrong wtf. this cant b true!
but thank u very much for ur efforts! perhaps i would try 2 restore a vendor img from sum1 which rom does work. i know its a great demand but could u send me urs? ;D i dont know if there r sum personal info..
best regards
Don't give up there might be a solution.
Pray to God for some help.
:good:
---------- Post added at 01:23 PM ---------- Previous post was at 12:59 PM ----------
Currently I am using Xiaomi.eu beta rom. You can check their website for all the features. Its smooth, stable and can update without needing to got the recovery:victory:
This should work for you because unlike other roms this is based on miui for riva. That means you will get updates till Xiaomi ditches support for riva.
I recommend you use this rom over the global rom until you fix the problem with your phone.
Some things missing:
Choice of region is limited( India is not available)
There is no custom kernel available for miui oreo as of now.
Magisk safetynet not passed
If you're going flash this rom you need to be on latest global beta fastboot rom and need a recovery that supports oreo base.
I use batik recovery base oreo.
yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway
daemonicvs said:
yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway
Click to expand...
Click to collapse
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.
NaAnBcEhEuL9A8K7 said:
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.
Click to expand...
Click to collapse
theres no difference between my device and yours... everybody must have this problem ;/
daemonicvs said:
theres no difference between my device and yours... everybody must have this problem ;/
Click to expand...
Click to collapse
Did you try edl method?
NaAnBcEhEuL9A8K7 said:
Did you try edl method?
Click to expand...
Click to collapse
yes. i could flash the stock rom this way but the problem is not solved this way
daemonicvs said:
yes. i could flash the stock rom this way but the problem is not solved this way
Click to expand...
Click to collapse
At least you have to try.
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
Did you flash lazy flasher?
Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
dont u have 2 wait 2 weeks or so till bootloader is unlocked?
what exactly do u mean with won't boot up? bootloop? or stuck at boot logo?
after flashing a custom recovery, did u boot directly into the system or did u try 2 boot into recovery? sometimes the stock recovery overwrites the custom 1 when stock rom boots up
my problem is solved. i remembered that i made a full nandroid backup with twrp before i flashed a new rom and the problem appeared. so i restored everything i backed up with twrp (incl cust) and voila, rom booted up. and i can wipe system and data and flash every rom i wanna and it still boots up \o/
i really could have tried it earlier but i didnt think of this untill yesterday ;D
well, thx for ur efforts anyway buddy @NaAnBcEhEuL9A8K7
cheers

i need help with restoring my samsung a50

my plan was to install pixel experience, i had the bootloader unlocked, and after installing twrp; i wasnt able to boot.
long story short i wiped literally everything in the advanced wipe section of twrp, including system, thinking ill be able to boot my phone.
what i need help with, is there a custom rom which doesnt require an existing boot or os to run? or i can install stock rom from sammobile through odin and will it work that way?
i saw this on yt comments, wanted to know if it is correct, "When I inquired a bit about GSI ROMS, I saw that these ROMs doesn't flash over the boot partition, they use the currently installed one. Because of that you probably have a broken boot partition causes bootloop."
i am able to enter twrp and download mode from there.
thank you.
did you flash patched vbmeta?
VD171 said:
did you flash patched vbmeta?
Click to expand...
Click to collapse
helo thanks for the reply, I dont know what vbmeta is, can I ask for an explanation?
peachlove said:
helo thanks for the reply, I dont know what vbmeta is, can I ask for an explanation?
Click to expand...
Click to collapse
Vbmeta verifies if any partitions was changed.
If it was, then it causes a bootloop if bootloader is locked.

Question Poco F3 - Boot Loop to POCO logo / Please help

Hello.
I have a big problem after updating the firmware.
Poco F3 root over magisk.
After updating from 12.5.6.0 RKHEUXM, I updated to 12.5.7.0 RKHEUXM.
After the restart, both the phone and the system booted up.
I patched the original boot.img via magisk, which I extracted via the Payload Dumper utility.
I flashed the patched boot.img in fastboot and after the reboot my phone went to the bootloop for the MIUI logo.
I tried to flash back the original boot.img and the bootloop is still, but now following the POCO logo, not the MIUI logo.
After a few bootloops, the phone stays in fastboot.
It's never happened to me before.
Twice before that, after the update, I normally flashed patched_boot.img and everything was fine, no bootloop.
Please who can advise me how to boot back into the system without losing data.
Thank you very much, I'm clueless.
Re flash stock rom
how please Re flash stock rom? detailed instructions, thanks
and I won't lose the data? (photos, videos)
edit:
Now i flash from fastboot the original boot.img to AB partition and bootloop to MIUI logo, after a few bootloops phone stays in fastboot
Format data in recovery.
hexisg said:
Format data in recovery.
Click to expand...
Click to collapse
So re flash stock rom or format data?
These are two different answers.
And when format data, so in stock recovery??
And I won't lose my data, like videos, photos, etc.?
nobody help?
How re flash stock rom over ADB or TWRP without loose data?
How re flash stock rom over twrp? please
If you have a bootloop you need to format data.
Always back-up you data.
Solved:
wipe dalvik/cache over TWRP
jkmaxfli said:
Solved:
wipe dalvik/cache over TWRP
Click to expand...
Click to collapse
about your phone: i want to buy this model, is so really great as people says?
JUAN139 said:
about your phone: i want to buy this model, is so really great as people says?
Click to expand...
Click to collapse
For me yes.
JUAN139 said:
about your phone: i want to buy this model, is so really great as people says?
Click to expand...
Click to collapse
its superb
JUAN139 said:
about your phone: i want to buy this model, is so really great as people says?
Click to expand...
Click to collapse
In my opinion you can be a bit disappointed only with camera. Rest is as good as ppl say. I have got F3 too.

Question stuck on boot logo (fixed)

booting to fastboot after flashing with mtk, finally unlocked the bootloader so it's easier... what do i do?
i have: orangefox recovery from another xda thread here (best recovery ever)
i dont have: a stock super img because i also wanted to flash a gsi
Edit: fixed but its now stuck on boot logo
2nd Edit: fixed by installing miui 13.0.2 (IM EXCITED)
itayalush said:
booting to fastboot after flashing with mtk, finally unlocked the bootloader so it's easier... what do i do?
i have: orangefox recovery from another xda thread here (best recovery ever)
i dont have: a stock super img because i also wanted to flash a gsi
Click to expand...
Click to collapse
What do you want to do?
SubwayChamp said:
What do you want to do?
Click to expand...
Click to collapse
to get miui work again
oh wait i fixed this but now its stuck on the logo and after a few hundred years it turns off + i really want someone to make a custom rom for this device
itayalush said:
to get miui work again
Click to expand...
Click to collapse
Flash the stock ROM
I know what happened
He flashed orangefox to boot but orange fox can't flash to boot because then you can't boot the os I had the same problem
You have to copy orange fox and original boot.img to your phone. Flash the original boot.img and then flash orangefox recovery ramdisk however I don't know because I only know how to install TWRP this way
SubwayChamp said:
Flash the stock ROM
Click to expand...
Click to collapse
i did, like a million times
Stephanizgo said:
I know what happened
He flashed orangefox to boot but orange fox can't flash to boot because then you can't boot the os I had the same problem
Click to expand...
Click to collapse
i also tried with stock boot... result: still stuck on boot logo
pls anyone help
i wiped cache partition so maybe it will finally work... pls give me other solutions while it's booting
itayalush said:
i wiped cache partition so maybe it will finally work... pls give me other solutions while it's booting
Click to expand...
Click to collapse
Format data
Stephanizgo said:
Format data
Click to expand...
Click to collapse
tried a million times before
itayalush said:
i did, like a million times
Click to expand...
Click to collapse
Tell me exactly, so, I can help you.
When you unlocked bootloader, which other partitions you formatted? You said, you used "mtk", I assume you used ,mtk-client, and in the scripts of this tool, also is recommended to delete other partitions.
When you say, you flashed back the stock ROM, which method did you use?, which tool?, and what message you got from that tool, I mean, it was success, etc?
I recommend replacing Orange Fox with TWRP.
I just had this issue on a different Xiaomi phone. I replaced Orange Fox with TWRP and was able to flash LOS and fix the problem.
SubwayChamp said:
Tell me exactly, so, I can help you.
When you unlocked bootloader, which other partitions you formatted? You said, you used "mtk", I assume you used ,mtk-client, and in the scripts of this tool, also is recommended to delete other partitions.
When you say, you flashed back the stock ROM, which method did you use?, which tool?, and what message you got from that tool, I mean, it was success, etc?
Click to expand...
Click to collapse
i flashed my stock rom after finally unlocking my phone after millions of tries with the "Unknown Error -1", i finally found a modified unlock tool that fixes it. still stuck on boot logo
if you want my unlock tool, this is the file (u can publish it wherever you want)
Oh... nevermind... I just installed MIUI 13.0.2 and it's back to its normal state (Just without the data because I wiped it a way before I unlocked the bootloader)
itayalush said:
Oh... nevermind... I just installed MIUI 13.0.2 and it's back to its normal state (Just without the data because I wiped it a way before I unlocked the bootloader)
Click to expand...
Click to collapse
So you were trying to boot Xiaomi on unverified software on locked bl the mtkflash bypassed bl and installed by itself how is that possible
You can now install my TWRP lol
Stephanizgo said:
So you were trying to boot Xiaomi on unverified software on locked bl the mtkflash bypassed bl and installed by itself how is that possible
Click to expand...
Click to collapse
No, they unlocked the bootloader, as it said in the first post.
SPFT and mtk-client tools can flash even to locked devices.

Categories

Resources