Database Users

Can't boot after installing open gapps

I'm trying to install LineageOS + Open Gapps on my nexus 4, but I get stuck on bootloop
This are the steps I follow:
1. Reboot into bootloader and flash latest version of TWRP recovery.
2. From recovery, wipe every partition.
3. Resize partitions using parted so system partition is now around 1.5Gb (taking space from userdata)
4. Sideload last version of LineageOS
5. For some reason, after step 4 /system is again around 800Mb so I need to resize it again to 1.5Gb to have enough room to install OpenGapps. I do from TWRP: Wipe --> Advanced wipe --> Repair or change file system --> Resize system partition.
6. Now I sideload the Gapps package, without any issue.
7. Try to boot system, but it spend around 2 minutes trying to loading it and then reboots into recovery.
I have tried with any version of OpenGapps and it's the same, the OS wont boot.
If I try to boot the system after step 5 (resizing system partition), the OS boots fine and everything is working.
Edit: Using an old version of OpenGapps (March/2018), the system boots and things work fine

Instructions

Hey there great people out there!
Can somebody provide me the correct instructions for installing any Oreo ROM? It's not that I am lazy to search, believe me I have tried But problems came like Internal storage is not showing up on twrp(encrypted).Thanks a lot!BTW I'm on marshmallow right now,so please provide on how to update from marshmallow ?

Tech x 125 said:
Hey there great people out there!
Can somebody provide me the correct instructions for installing any Oreo ROM? It's not that I am lazy to search, believe me I have tried But problems came like Internal storage is not showing up on twrp(encrypted).Thanks a lot!BTW I'm on marshmallow right now,so please provide on how to update from marshmallow ?
Click to expand...
Click to collapse
You said you are on marshnallow.. Detailed step below.
1. Update to the latest nougat firmware using ota. Because lateat firmware is needed for oreo roms. Else you will face tons of bugs and problems.
2. Download recovery from same thread of the oreo rom you are using. Oreo roms need vendor partition, so it needs recovery that supports it.
Download the rom and gapps also.
5. Copy the rom, recovery image and gapps into the memory card. Boot into fastboot mode. Connect to pc. You can boot to fastboot by using command "adb reboot fastboot" without quotes.
4. Unlock the bootloader by connecting to pc via fastboot.(steps to unlock is given in the xda guide section or k6 power.)
5. Boot into twrp recovery image using fastboot. Your phone will reboot to recovery.
6. Using recovery install the recovery image from it by going to "install option" then selecting file type as image and selecting recovery image file.
7. Reboot recovery.
8. Format data to remove encryption. After that you can access internal storage. Wipe data, cache, dalvic cache, system, data and internal storage.
9. Flash the rom file. Flash the gapps.
10. Reboot to system from twrp.
If you can understand any steps above you can google. If you cant understand google, then forget about doing it. Because you will eventually break your phone. Give it to someone who knows in that case.

Lol I will not brick my device.I can get back to marshmallow anytime!The only problem I was having before was the device wouldn't show anything(0mb) on internal storage on booting in the ROM.Is this normal.Maybe the ROM is encrypted.On nougat this is not happening on any ROM.Currently Iam on nougat(stock).It shows internal storage only after formatting data but reinstalling the ROM and booting again in recovery it shows 0mb on internal storage.

Tech x 125 said:
sk.vyshak said:
You said you are on marshnallow.. Detailed step below.
1. Update to the latest nougat firmware using ota. Because lateat firmware is needed for oreo roms. Else you will face tons of bugs and problems.
2. Download recovery from same thread of the oreo rom you are using. Oreo roms need vendor partition, so it needs recovery that supports it.
Download the rom and gapps also.
5. Copy the rom, recovery image and gapps into the memory card. Boot into fastboot mode. Connect to pc. You can boot to fastboot by using command "adb reboot fastboot" without quotes.
4. Unlock the bootloader by connecting to pc via fastboot.(steps to unlock is given in the xda guide section or k6 power.)
5. Boot into twrp recovery image using fastboot. Your phone will reboot to recovery.
6. Using recovery install the recovery image from it by going to "install option" then selecting file type as image and selecting recovery image file.
7. Reboot recovery.
8. Format data to remove encryption. After that you can access internal storage. Wipe data, cache, dalvic cache, system, data and internal storage.
9. Flash the rom file. Flash the gapps.
10. Reboot to system from twrp.
If you can understand any steps above you can google. If you cant understand google, then forget about doing it. Because you will eventually break your phone. Give it to someone who knows in that caseencryptedThanks Man!
Lol I will not brick my device.I can get back to marshmallow anytime!The only problem I was having before was the device wouldn't show anything(0mb) on internal storage on booting in the ROM.Is this normal.Maybe the ROM is encrypted.On nougat this is not happening on any ROM.Currently Iam on nougat(stock).It shows internal storage only after formatting data but reinstalling the ROM and booting again in recovery it shows 0mb on internal storage.
Click to expand...
Click to collapse
Reinstalling the rom means it is again getting encrypted. By default encryption is on in stock rom. So you have to format data to break encryption. Otherwise you cant access internal storage. You need latest firmware (nov security patch) for oreo roms.
Click to expand...
Click to collapse

thanks
sk.vyshak said:
You said you are on marshnallow.. Detailed step below.
1. Update to the latest nougat firmware using ota. Because lateat firmware is needed for oreo roms. Else you will face tons of bugs and problems.
2. Download recovery from same thread of the oreo rom you are using. Oreo roms need vendor partition, so it needs recovery that supports it.
Download the rom and gapps also.
5. Copy the rom, recovery image and gapps into the memory card. Boot into fastboot mode. Connect to pc. You can boot to fastboot by using command "adb reboot fastboot" without quotes.
4. Unlock the bootloader by connecting to pc via fastboot.(steps to unlock is given in the xda guide section or k6 power.)
5. Boot into twrp recovery image using fastboot. Your phone will reboot to recovery.
6. Using recovery install the recovery image from it by going to "install option" then selecting file type as image and selecting recovery image file.
7. Reboot recovery.
8. Format data to remove encryption. After that you can access internal storage. Wipe data, cache, dalvic cache, system, data and internal storage.
9. Flash the rom file. Flash the gapps.
10. Reboot to system from twrp.
If you can understand any steps above you can google. If you cant understand google, then forget about doing it. Because you will eventually break your phone. Give it to someone who knows in that case.
Click to expand...
Click to collapse
thanks

How does one go about installing a GSI ROM on the Realme 2 Pro?

Hi!
Could someone please give a step-by-step guide as to how one would go about installing a GSI ROM on the Realme 2 Pro (4GM RAM version)?
And which ROM do I download, A only, or A/B? Is it ARM 64?
I had tried once before, and messed up.
Hoping someone is able to help me out here.
Thanks!

Now only mid stable rom Havoc-OS-v2.0-20181027-GSI-ARM64-Aonly
Use only Arm64-Aonly
0.Always Make Backup System,Efs,Data & Vendor partition
1.first boot twrp
2.swipe factory reset
3.Twrp advanced option Format System,Data,Delvik Cache & Cache
4.Now Install System image of havoc gsi arm64-aonly image to system
5.When install completed then wipe cache & delvvik cache
6.Then swipe to reboot
7.Ready to go
8.but this rom not for daily use,many bug present,Fingerprint not working

galibalmasanick said:
Now only mid stable rom Havoc-OS-v2.0-20181027-GSI-ARM64-Aonly
Use only Arm64-Aonly
0.Always Make Backup System,Efs,Data & Vendor partition
1.first boot twrp
2.swipe factory reset
3.Twrp advanced option Format System,Data,Delvik Cache & Cache
4.Now Install System image of havoc gsi arm64-aonly image to system
5.When install completed then wipe cache & delvvik cache
6.Then swipe to reboot
7.Ready to go
8.but this rom not for daily use,many bug present,Fingerprint not working
Click to expand...
Click to collapse
So I decided to try this out. And once I swiped to reboot, it showed "No OS installed. Do you want to continue?". When I restored from my backup, it would boot up, reach the homescreen, and the immediately restart. I have no idea what more I can do now.

Do you flow these script carefully?just extract havoc os zip,you will get havoc system img then just flash image file to system,then install nano gapps,then wipe cache & delvik cache with data just swipe for reboot,you can go perfect.

Get any ARM64 a only GSI rom. Our device only support ARM64 a format.
1 Put system image wherever sutable to you.
2. Take a full system backup.
3. Go to wipe and just swipe to factory reset.
4. Click on install and select system image and flash that image in system partition.
5. After flashing just reboot.
Process is simple.

Brother do you try bliss rom link - https://forum.xda-developers.com/pr.../rom-blissroms-9-0-official-4-4-2019-t3918303
i tried this.here is some screenshot
https://imgur.com/rBKNRQQ
https://imgur.com/Q7g68mR
https://imgur.com/bEKYvS8
https://imgur.com/nDkrhiH
https://imgur.com/mddj5yk
https://imgur.com/xfN23Yp

Ashwinrg said:
Get any ARM64 a only GSI rom. Our device only support ARM64 a format.
1 Put system image wherever sutable to you.
2. Take a full system backup.
3. Go to wipe and just swipe to factory reset.
4. Click on install and select system image and flash that image in system partition.
5. After flashing just reboot.
Process is simple.
Click to expand...
Click to collapse
Any twrp can be used ?
No need to flash vendor.zip ?

Ashwinrg said:
Get any ARM64 a only GSI rom. Our device only support ARM64 a format.
1 Put system image wherever sutable to you.
2. Take a full system backup.
3. Go to wipe and just swipe to factory reset.
4. Click on install and select system image and flash that image in system partition.
5. After flashing just reboot.
Process is simple.
Click to expand...
Click to collapse
So I tried this, and still did not manage to get it working. In fact I somehow managed to completely brick my phone, where I could neither access the OS, nor the bootloader. I had to take it to the service centre.
I even tried flashing the vendor zip file. But to no avail.
Is there perhaps a video which show the steps from top to bottom, starting at the bootloader unlock? (I want to make sure I'm not really messing that up either)

[Guide][GSI][R]Andriod R[MI NOTE 3][JASON]

This works for any device that supports project treble...Thanks to all developers involved in this work
Requirements:
Must have Unlock Bootloader
Must-Have Custom Recovery
How to install:
1.Install a custom recovery Jason
2.Install vendor IMG for your device...(I used a simple workaround here. flash a custom ROM then reboot into recovery wipe cache data and system don't wipe 'vendor')...if you have a question you can ask me, Danny
3.Install Android 11 img into system partition(select install IMG not install zip then select system under partition) https://tweakguy.com/download-android-11-gsi-rom-for-any-phone/ (you must extract the downloaded zip to get IMG file)
4.Reboot (may take up to 10mins)
5.Enjoy

Android 11 preview version has a lot of bugs：p

[Q] [HELP] Odin/TWRP Flash successful, BUT not changing anything after reboot

TLDR : I Cannot MODIFY ANYTHING IN SYSTEM or USERDATA(i.e. internal storage) partitions. Files Deleted via twrp in System/internal storage comeback after reboot and new files added from computer vanish after reboot. Also NOW, different flashes are successful through both methods via -
1. twrp recovery-(Boot/recovery/CustomROMs flashes) and
2. ODIN-(boot/recovery/Stock ROM flashes)
but again dont change anything after reboot (previously both methods worked, so no issue with twrp or odin according to me). So, Whole storage (System+Internal Storage) is intact after Reboot as it is. Now I feel it has something to do with magisk. I can see exact file names both in internal storage and /system and do delete, move, rename i.e. any operations in twrp so i guess storage is not encrypted. I can boot into system for hardly 10-15 seconds after that it bootloops again, so i cannot do anything there. Only options to me is twrp recovery or odin, both are not helping for now.
--------------------------------- DETAILED EXPLANATION : ------------------------------------
[PROBLEM 1] DELETION:
Anything deleted via TWRP recovery in system partition or "EVEN in sdcard, i.e. internal storage" deletes successfully in twrp, without any error but comes back in the same state after the reboot. When i delete error causing file or folder via TWRP file manager, it gets deleted, and if you check again it's not there wherever it was present, but just after reboot every file and folder comes back to previous state like if nothing was done. This is true for any file present in any of the partitions. Newly inserted file in internal storage vanishes after reboot, and deleted file comes back after reboot - true for any partition. Status quo maintained !!
[PROBLEM 2] FLASHING:
To solve above problem, i thought it might be an issue with Magisk or the new twrp recovery, so i tried flashing Magisk Uninstaller zip in twrp, which again flashes successfully, SECONDLY- tried zackptg-(dmverity,forceencrypt Disabler) zip file, that also flashes successfully(i thought might be an issue of dmverity or encryption), and THIRD thing i tried flashing older twrp version recovery, that also flashes successfully but after reboot same currently installed twrp boots, not the newly "successfully flashed" older version. So i cannot change twrp-(tried both recovery.img flash in (1) twrp itself and (2) also through ODIN) - both returns flash successful and pass(in Green). FOURTH, tried dirty flash both (1) other ROM and (2) SAME ROM on top of current ROM- everything returns successful but after reboot boots the current erroneous ROM that i want to change. FIFTH, tried Clean Flashing i.e. wiped everything (selected 1. dalvik cache, 2. data, 3. cache, 4. system, 5. Internal Storage in wipe section) and also tried Factory RESET and FORMAT DATA option and after all this flashed Custom ROM zip file only (no gapps or magisk flash), but every wipe operation returns successful and ROM flash also successful, but when reboot into system again that bootlooping erroneous ROM that was present before all of these "successfully done" operations.
[PROBLEM 3] ODIN FLASH:
As all above failed, i thought flashing STOCK ROM through ODIN is my last resort. I did (1) Stock recovery flash through Odin- it was green pass (successful), but when booted returned that same twrp recovery not stock recovery. Tried (2) flashing Stock BOOT.img flash through ODIN, again it was successful but actual boot resulted the same Magisk Patched Boot.img. Third (3) tried flashing whole STOCK FIRMWARE - Official latest Stock firmware that was extracted from Samsung Smart Switch, with default options turned on in Odin, flash was again green-pass(successful) but auto reboot after successful flash through ODIN resulted same old erroneous ROM booting up like a VAMPIRE (I'm not dead, I'm Alive!!)... Fourth (4) tried flashing Stock Firmwave of step 3 with NAND ERASE and RE-PARTITION options turned on by inserting pit file to do BANG BANG, nuking my phone with these options that many people on internet advise not to use, screenshot attached below( it took 42 minutes to complete ), again using these options nand erase and re-partition also resulted successful(green-pass) and resulting that same untouched state as it was before.. Boots into twrp recovery not the stock rom or stock recovery with that same old erroneous ROM present in system with data partition intact. (Tried using different ODIN versions, different USB ports on my laptop, different non-official firmwares(but these non-official firmwares of SM-G530H resulted in some errors in ODIN, i.e. it was not green pass like that of official firmware, but resulted RED FAIL.))
[PROBLEM 4] SYSTEM_ROOT Created:
This i saw for the first time i guess, in my phone, and maybe the cause of this whole problem. Now my root directory in twrp '/ ' contains /system_root along with /system, /data, /cache. One more thing /system_root contains system folder ,i.e. /system_root/system results same things as /system . When checked in twrp>wipe section> Repair system> There System Mount Point is shown as : /system_root instead of previously used to be "/system" normal directory when /system_root was not present at all.
Another thing /system_root contains files like default.prop , init files, sepolicy which are also present in root directory ' / ' . This whole /system_root should not have existed at all when /system exists. Maybe /system_root or the init files or other thing present inside /system_root are preventing all the changes - deletion , flashing changes etc. described in this post and maybe this folder was created by step(3) flashing procedure below , i.e. due to magisk. Also formatting system in twrp>wipe>system returns successful msg but nothing is deleted when checked in twrp file manager or twrp>Backup (system partition backup size shows 1456 mb even after formating)
[OTHER THINGS I TRIED] to solve this -
- Deleting twrp folder to make it to default state, again it's successfull deleted but doesn't loads default configuration after reboot due to PROBLEM 1 above as deletion reverts back after reboot
- Fixing contexts in twrp
- reboot disemmcwp
- mount -o remount,rw /system commands in twrp terminal (again to mention every command that is possible to enter runs without any error, hence successful but problem persists even after that )
- flashing stock boot.img and recovery.img (both successful no changes observed after reboot, but after stock boot or recovery.img flash, if you flash magisk uninstaller zip it still says "magisk patched image detected", and next thing written after it is " ! (Exclamation mark) Boot image backup unavailable" , then "Restoring ramdisk with internal backup" again magisk uninstaller also returns successful. after reboot again runing uninstaller detects magisk again. and boots twrp only instead of stock recovery
- repair, resize system partition in twrp>wipe section results Twrp error 1 (might be due to that /system_root folder that contains now /system which is also present in ' / ' root
- Changing "system partition" file-system with all 6 options returns successful but filesystem stays ext4 only when checked again.
WHAT IS WORKING-
Odin is working. - i once flashed my first twrp recovery on this device through the same version
TWRP is working - Although this is new twrp version 3.6.1_9-0 that i flashed just few time before all this catastrophe happened (maybe it might be the cause or it may be magisk)
Current Configuration:
Device: Samsung Galaxy Grand Prime
Model: SM-G530H (fortuna3g)
ROM: [STABLE][10] LineageOS 17.1 GO by DarkDroidDev from xda
GApps: Customised OpenGapps package (this caused erroneous bootlooping ROM) - i can boot into ROM but it is very lagging, and reboots again after some time, ranging from 10-20 seconds to max 3 minutes. Launcher is not working. And Keyboard is crashing. I can go into settings to change something but change doesn't persists after reboot
Magisk: Magisk 23.0
What was my FLASH PROCEDURES before this happened-
- Cleaned dalvikcache, data, cache, system
- After this, Data and Cache showed 0mb in Backup option in twrp, system showed 2mb containing only usr folder, boot showed 13mb
- (1) Cleaned Flashed above ROM
- (2) Customized OpenGapps flash
- (3) Magisk Patched Boot.img flash - - (not magisk.zip installer, its magisk-patched-boot.img flash through twrp only)
- (4) Dalvik Cache Wipe
- Booted into System.
I was actually testing the customised OpenGapps package,
Before this flashed customised package 10-20 times. i was editing, flashing, seeing the changes... > then again editing, flashing. So this was not the first time.
If any error occured, like launcher not working, i again booted into twrp wiped system data or deleted particular launcher file in twrp, all worked, changes were successful then i again continued my testing.. editing packages > flashing > seeing the changes by booting into actual rom.
But this whole case happened during the iteration of my testing when i introduced Gboard apk, downloaded from Play Store from fortuna3g(this device), into the Custom Gapps Package.
So, the cause of all this according to my knowledge where i doubt maybe one of the following-
(1) - That Keyboard apk installation as system app (most probably permissions problem, as apk was fine as tested before on this device and resulted in keyboard related folders created in that /system/usr folder which always contained only one folder, but only this time contained this keyboard related stuff there)
(2) - That magisk-patched-boot.img flashing procedure, step(3) above, just after openGapps flash "without booting into system first" - this was done first time in my testing iterations, so might be incorrect procedure
(3) - Due to step (3), issue might be related to magisk related stuff - dm-verity, Force encryption
(4) - Creation of /system_root folder in root directory '/ ' maybe due to step (3), there used to be only /system there before
(5) - Hardware Problem, maybe that's why all those successful twrp and ODIN flashes not doing anything
Please suggest something that i have not tried and could solve this PROBLEM of NOT BEING ABLE TO CHANGE ANYTHING ON SYSTEM or USERDATA partition.
I know people here know a lot more than me, and can help me with their valuable suggestions and solutions, if any.
Thanks.

I found one xda thread almost with same issue as mine titled -
[Q] Weirdest problem - flashing anythin thru ODIN does not change anything in my S4​But no working solution there also

LinhBT said:
Need to know exactly if it's Snap or not. If it is, then there're 2 options you can try.
1. Ask some one have the same device model as you, do a ROM dump ( you can google for more detail ). Once you got that, I can share with you the tool needed for restore your device from that dump.
2. Try find your device's Factory Images ( similar to Fastboot ROM, but a little different ), and an authenticated prog of your SoC ( this I can share too if you choose this option ) then boot your device into EDL mode by using fastboot2EDL script ( on Git, you can google too ) then use QFIL ( one tool in QPST Tools by Qualcomm ) and force flash the images into the device.
So far as my experience and understanding, there're only these 2 solutions to fix your device ( if it's Snap powered ).
Click to expand...
Click to collapse
Hi mate, My phone is Snapdragon powered..
My problem is almost similar.. But not exactly.. After almost 2 months I am not able to find a solution.. But after this period of researching and googling about things related to my problem.. I feel now, either any one of the following is the cause of problem:
1. Emmc is stuck or locked in read-only mode (Can move files from pc , delete already present files anywhere in any directory, but all changes vanish after reboot... all file and directory structure remain intact- moved files from pc gets deleted.. and deleted files which were already present come back after reboot )
2. Corrupted /data and /cache partition, as e2fsck in twrp terminal results shows "filesystem still has errors" and "e2fsck: unable to set superblock flags on /dev/block/mmcblk0p** ) in both these file system (I think they are preventing flashing procedures- Odin stock firmware flashes and twrp custom ROM flashes both are successful, but after reboot no changes can be seen... - Even Recovery.img and boot.img flashes don't seem to work even both are shown successfully flashed in twrp) After reboot current version twrp boots again instead of newly flashed different version recovery.img ... same with boot.img even after running magisk uninstaller zip files.. running uninstall.zip 2nd or 3rd time also shows magisk patched image detected in log which should be removed in 1st iteration itself..
3. Might be magisk is preventing these changes to be made.. or It might be the /System_root creation as mountpoint for system partition which used to be previously /system normally. This might be the superblock creation which not used to be there. You can see my attachments in my thread to see my directory structure of system_root and my download mode picture
My Samsung's twrp and Download Mode seems to be working but no changes made by them even after successful operations by both.
Can you suggest anything @LinhBT ?