Hello people.
I am trying to install a Rom + working Google Play Store for 6 hours now and I have no luck.
I tried CM13, Dirty Unicorn and Slim. None worked.
GApps I tried: OpenGapps 6.0 Pico, Banks Dynamic, DU Gapps Black. All for 6.x.x
I am using TWRP 2.8.7.0 .
Now when I flash the GApps, the old Play Store is installed, which doesn't have Pokemon Go yet.
When I restart my phone, it updates(?) somehow and I can see Pokemon Go.
Now after this update, I am unable to install any App.
It is really frustrating for me.
Procedure I follow in TWRP:
1. Wipe Cache/System/Data
2. Choose the Rom + add more zips -> and than the GApps.
3. Wipe Dalvik
4. Reboot.
I would hope for help guys!
Downgraded to 5.1 (SkyDragon 8.0) and it works there. It is a Marshmallow problem as it happened on ViperOne 9.0.0 as well for me.
Hello out there,
my problem is a bit annoying. Everything is fine if I use my OP3T with Oxygen (4.0.3) and TWRP (3.0.3-1). But I want to use LineageOS with TWRP and cant, because my TWRP isnt working after flashing lineage.
"Normal"-Setup:
- TWRP 3.0.3-1
- Oxygen 4.0.2 or 4.0.3 (doesn't matter)
- supersu 2.79
- Encrypted Device
"Lineage"-Setup:
- TWRP 3.0.3-1
- lineageOS (lineage-14.1-20170214-nightly-oneplus3-signed.zip OR lineage-14.1-20170208-nightly-oneplus3-signed.zip - tried both, doesnt matter)
- supersu 2.79
- openGApps for 7.1 nano
- Encrypted Device
My Problem is, that I can boot up lineage and use it, but if I reboot into my TWRP to flash something or make some Backups, it asks for my encryption-passphrase, it says it is okay and boots into the twrp main-windows. After that I can't touch anything (stuck in mainmenu) and after a few seconds it results into a black screen (plus white LED) and I am forced to reboot the device. After that reboot I have to reconfigure lineage (seems to loose data).
Does anyone have an idea how to fix this annoying "bug"?
Thank you very much!
Atomique
EDIT: I found that Thread after searching for a issue like that in the lineageOS official Thread - I will try this and report! - Thank you! https://forum.xda-developers.com/on.../recovery-official-twrp-oneplus-3-3t-t3543391
I had the exact same problem when I hab LineageOS installed! It would always lose all its data. After flashing and reflashing a hundred times, I ended up reverting my OP3T back to stock using a OnePlus forum guide (I'm a new user, so I can't post the link). I am now back to OOS 4.0.3 but can't even get SuperSU to work. Whenever I flash it (with or without the dm-verity fix) the phone is stuck booting forever.
I found the post you linked to aswell but haven't tried flashing LineageOS using the new TWRP. But I can tell that the new version doesn't help rooting OOS...
Did you have any luck flashing LineageOS by now?
Edit: With the newest Lineage Version I always get an error when trying to flash it. Do you have the same problem? The nightly from two weeks ago seems to work better.
Use latest TWRP 3.0.4.1
nitinvaid said:
Use latest TWRP 3.0.4.1
Click to expand...
Click to collapse
That's what I'm doing... Could the dm-verity be a problem? There are two versions, one with opt and one with force in the name.
Thank you for your replies! The link (TWRP 3.0.4-1) worked like a charme!
@Tafelbomber: I would recommend you to start from scratch. But please be warned: you will loose your data! Make a backup first!
1. Delete everything with fastboot -w
2. Flash the recovery noted in my first post with fastboot flash recovery <twrp-filename.img>
3. Optional: Restart into the TWRP and flash the OOS 4.0.3 to make sure that you have a clean OS installed befor flashing lineage
4. Flash lineage OS + additional ZIPs (like supersu, betterbatterystats, Gapps etc)
5. Clean Dalvik and Cache!
6. Reboot and have fun. --> Sometimes you get problems with the encryption chain (Red Error --> in my case the fastboot -w did it for me)
Good luck - I will close this thread - thanks again for your help!
Atomique
EDIT: I want to close this thread, but I don't know how.
UPDATE: Hi guys, it me again.. I finally solve my problem with my phone Samsung S6 Edge SM-G925F.
first of all, I want to thank you Xda community who help to fix this problem and it was great to have very kind people
this solution only happen with my device samsung s6 edges, I am not sure about other devices, but here it goes
1.) go to https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
2.) download latest zip
3.) remember! uninstall ur Magisk first and make it clean
4.) flash those zip file from no-verity-opt-encrypt-6.x.zip and reboot but never install Magisk yet! NEVER!
5.) Wipe all cache.. and reboot, make sure it reboot properly, OK.
6.) proceed go to recovery TWRP and flash Magisk 15.0
7.) this will take 10-20 minute, after reboot success.. install Magisk Apps
8.) you will notice that u already got latest version of Magisk
for more detail about what just you read.. please read more from this thread
https://forum.xda-developers.com/apps/magisk/fix-bootloop-issue-magisk-14-6-15-0-t3725962
Special thanks to
Aria.A97 (starting thread I found)
Lemmy (solution from him)
-----------------------------------
Hi, I own samsung s6 edges SM-G925F
the older version of Magisk 14.3 working nicely on samsung s6 edge
but latest Magisk version 14.6 and 15.0 not working at all and stuck at samsung logo ..
my mission of this thread is to get the latest version 15.0 working on samsung s6 edges with help of xda community
here is what I just did
I upgrade Magisk 14.3 from the apps manager itself (5.4.0), and start rebooting
after that I stuck on samsung logo for about 24hour, I then proceed to wipe all data and lost everything and start from stock firmware again.. (ODIN)
after that
I install Samsung latest stock firmware again nougat 7, and flash custom recovery TWRP
and I install Magisk 15.0 from recovery, after installation finish without any problem I start to rebooting..
but same thing happen... stuck at samsung logo for very long time .. more than 5-10hour (this is not right)
I try to uninstall this latest version and reinstall Magisk (v14.3) again using TWRP.. I rebooting and it working again (waiting time only 20 minute and not an hour)
on the screen, I have Magisk app manager version 5.4.0, and it ask me to update to latest version again.. I know that if I update to
latest version , same thing will happen.. stuck at the boot loop and I don't understand why
I try again this time, it updating my Magisk app manager from 5.4.0 to 5.5.0 and also 5.5.1 (even latest by today)
I install Magisk v15.0 from the apps again and start rebooting.. after rebooting.. same thing happen! stuck in samsung logo
To conclude....
- I download everything only on XDA official thread including (Magisk Zip, Magisk Apps manager and Magisk Uninstaller) ALL IS LATEST
- I did Wipe all cache, delvick cache
- I did do factory reset
- I did many times wipe all cache
- I did manually flashing Magisk via recovery with TWRP (latest version as today)
- I did follow the instruction in Magisk official thread one by one
- but still stuck at the samsung logo for many hour and never recover.. untill I flashing older version magisk 4.3 to make it work again
I just cannot get this latest version Magisk 15.0 , only working for me is Magisk 14.3 without problem
please help.. I really want latest version with huge improvement
My devices info
- SM-925F
- Samsung S6 Edges
- International version
- Android 7.0
- Stock kernel 3.10.61-12414727
- Android security patch level 1 December 2017
4us said:
Hi, I own samsung s6 edges SM-G925F
the older version of Magisk 14.3 working nicely
but for latest version Magisk 14.6 or 15.0 not working
here is what I just did
I upgrade magisk 14.3 from the apps manager (5.4.0), and start rebooting
after that I stuck on samsung logo for about 24hour, I then proceed to wipe all data and lost everything and start from stock firmware again.. (ODIN)
after that
I install Samsung latest stock firmware again nougat 7, and flash custom recovery TWRP
and I install Magisk 15.0 from recovery, after installation finish without any problem I start to rebooting..
but same thing happen... stuck at samsung logo for very long time .. more than 5-10hour (this is not right)
I try to uninstall this latest version and reinstall version Magisk 14.3 again using TWRP.. I rebooting and it working again (waiting time only 20 minute and not an hour)
on the screen, I have Magisk app manager version 5.4.0, and it ask me to update to latest version again.. I know that if I update to
latest version , same thing will happen and I dont understand why
I try again this time, it updating my Magisk app manager from 5.4.0 to 5.5.0 and also 5.5.1 (even latest by today)
I install Magisk v15.0 from the apps again and start rebooting.. after rebooting.. same thing happen! stuck in samsung logo
- I did Wipe all cache, delvick cache
- I did do factory reset
- I did many times wipe all cache
- same thing happen..
I just cannot get this latest version Magisk 15.0 , only working for me is Magisk 14.3 without problem
please help.. I really want latest version with huge improvement
My devices info
- SM-925F
- Samsung S6 Edges
- International version
- Android 7.0
- Stock kernel 3.10.61-12414727
- Android security patch level 1 December 2017
Click to expand...
Click to collapse
Did u try flashing Magisk v15.0 zip manually via TWRP & not installing from the app? If not, give it a go. If it boot loops, you can flash v14.3 again.
Sent from my Moto G3 Turbo Edition
Grab a logcat when the device is bootlooping and then upload that together with the Magisk debug log (you can pull it from /data/adb/).
Yup, seeing a similar thing on a Samsung Galaxy Tab S2. Upgrade to 15 looked like it worked, rebooted, now stuck on the throbbing Samsung logo, can't get back in to Android
Help!!
I have the same problem as your only version that I see stable in this team is the 13.3 that passes the safety net the other versions like 15 and 14.6 are left in boot infinite I have the Android version just like you with the same security patch December 1, 2017 I look forward to prompt help to update the magisk
My device
SM-925I
---------- Post added at 11:31 AM ---------- Previous post was at 11:26 AM ----------
Have you achieved to operate the samsung pay mini with magisk?
Same problem SM-G925F nougat 7.0 stock magisk 14 - > 15
OMG i stucked on boot with 15.0 too. Whats the problem. What is the solution??
EDIT i have the solution right now tested it and working. download magisk unistaller and magisk 14.0. Enter the twrp first flash magisk uninstaller and after that flash magisk 14.0. Here we go
Also I do not work new versions !!!
By popular demand:
Grab a logcat when the device is bootlooping and then upload that together with the Magisk debug log (you can pull it from /data/adb/).
Try this method, with me on the S7 edge Nougat 7.0 Stock without any problem Magisk v15:
What I did:
1. I cleaned the cache and data of the magisk manager application and uninstalled it
In TWRP I made:
2. Magisk uninstaller
3. I restored the stock boot
4. I installed the latest version of Magiskv15
5. Reboot and everything works
I couldn't find a way to recover (I didn't know about the Magisk uninstaller), so I ended up ODIN flashing the whole Tab and am having to set everything back up from scratch again. Bummer.
edit: And just for fun since I was wiped already, I tried the Magisk 15 zip on a 100% clean device. Immediately hung at throbbing Samsung screen on boot. No action at all.
So yeah, it looks like Magisk 15 is a no go on newer Samsung stuff. I did upgrade my Nexus 5 to v15 with no issues :\
edit2: Magisk 15 -> Fail to boot -> Flash Magisk Uninstaller -> Flash Magisk 14 -> Successful boot!
So if I would have done the uninstall and re-flash, I probably could have recovered with out wiping the whole device. Bummer
Hope this helps some people...
Same thing on Honor 8 when I updated via MM > bootloop
Uninstaller didn't worked > bootloop
I backup with old twrp nandroid backup ^^
Tried again flashed v15 via twrp > bootloop
Tried with v14.6 > bootloop
Can't anymore install/root Magisk :'( :'(
Someone have a older of 14.6 version maybe I could try
same...
1. magisk 14.5 -> update (from app, install mode: direct flash)-> install v15 reboot -> Samsung Logo ( ~ 10 min )
2. TWRP -> uninstall magisk -> wipe cache & dalvik -> install 14.5 -> Boot (and reboots) OK
3. Reboot TWRP -> update/install v15 -> reboot System -> Samsung Logo :/ ( ~ 10 min )
again ... step 2
4. Reboot TWRP -> update/install v15 (wipe cache & dalvik after) -> Samsung Logo :/ ( ~ 10 min )
again ... step 2
5. TWRP -> uninstall magisk -> wipe cache & dalvik -> install 15.0 -> Samsung Logo :/ ( ~ 10 min )
again ... step 2
6. TWRP -> uninstall magisk -> (No wipe) -> install 15.0 -> Samsung Logo :/ ( ~ 10 min )
etc ...
SM-G925F -> SuperStock S8 by BugTracker UP1 -> magisk 14.5 = No probs ....
--- EDIT ---
Spartacus500 said:
Try this method
Click to expand...
Click to collapse
ok ... lets try
--- EDIT2 ---
@Spartacus500 : Guess What .... Samsung Logo :/ ( ~ 10 min )
Doesnt work on my Redmi 3s either
I can confirm that Magisk 15 doesn't work on the G925K. Phone refuses to boot at all. I have to force it to restart into download mode before even am able to boot into recovery. Still trying to get it running without a hard format, but thus far it's not looking good for me.
I'm on Ultimate Nougat S8+ Port V2 ROM.
Update 1: Dirty flashing the ROM works.
Update 2: Dirty Flash worked up to the point of "optimising apps", once the process was finished, the phone rebooted and went into boot loop again. Doing system wipe now as I've got no choice.
NoGo on Axon 7 too. Updating thru Magisk Mngr succeded, but no root after. Reverted to v14.5 by TWRP is mostly working but the list of apps with root access is messed up - some apps have root access but not listed.
Guys have you tried flashing dm-verity disabler by jcadduono after flashing Magisk?
[Insert General Disclaimer Here]
Link: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
@Didgeridoohan That's so early in the boot process adb reports device as Offline so don't expect logcats from average Joe. Samsung Devices doesn't boot with custom recovery and dm-verity enabled, Magisk 15 no longer disables dm-verity by default so...
Aria.A97 said:
Guys have you tried flashing dm-verity disabler by jcadduono after flashing Magisk?
Link: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Click to expand...
Click to collapse
This is strange. I already had dm-verity disabled. Flashing 6.0 fixed the 15.0 problem. My phone successfully boots now despite having 15.0 (I'd already uninstalled it and flashed 14.0 onto it, but I reflashed 15.0 to check your suggestion out).
FallenAngelII said:
Unless the latest version of Magisk turns it on for some reason, it shouldn't matter. dm-verity was already disabled for me.
Click to expand...
Click to collapse
That's strange. I am using S6 running December 2017 Security Patch and Magisk 15 works just fine
Also quote from Magisk Thread:
If dtbo.img is detected on your device, KEEPVERITY is enabled by default. If your device is already encrypted, KEEPFORCEENCRYPT is enabled by default.
Click to expand...
Click to collapse
Aria.A97 said:
That's strange. I am using S6 running December 2017 Security Patch and Magisk 15 works just fine
Also quote from Magisk Thread:
Click to expand...
Click to collapse
I updated my post. It was dm-verity. Apparently, installing 15.0 magically turns it on again for some idiotic reason.
Hello to all.
So, I have the N950F (international Exynos) which generally works fine, but It started being weird for some reason. I installed TWRP on day one, used IronMan ROM since day one and everything worked. I still use IronMan 2.0 (Oreo) since I don't really like the One UI, and I debloated the ROM piece by piece until I overdid it and the Contacts app stopped working properly. When I tried reinstalling (with a full wipe), TWRP crashed and the device would bootloop, so, as usual, I redownloaded the zip (and verified checksums), and the exact same thing happened. As it turns out I can't install anything on the device, TWRP crashes on installation every time and the ROMs bootloop.
Observed hint: the installation always crashes on steps related to the boot image, regardless of bootloader version installed.
Steps taken: tried every available TWRP version (including unofficial ones), tried different bootloaders, tried different ROMs (Oreo and Pie), tried flashing with full wipe and dirty. The problem persists.
After the installation crash I sometimes get "E:Legacy property environment did not initialize successfully. Properties will not be detected.". Subsequent attempt results in Aroma claiming the ROM is for greatlte and current device is "" and stopping immediately.
backup/restore in TWRP works fine which turned out to be my saving grace.
Enclosed are TWRP logs including a large last_log from /cache/recovery and a screenshot of current system version (but the problem persists on every bootloader/system configuration). I went through them, but couldn't find anything relevant, so any help will be greatly appreciated. I might be just dim and missing something obvious.
TalkingChicken said:
Hello to all.
So, I have the N950F (international Exynos) which generally works fine, but It started being weird for some reason. I installed TWRP on day one, used IronMan ROM since day one and everything worked. I still use IronMan 2.0 (Oreo) since I don't really like the One UI, and I debloated the ROM piece by piece until I overdid it and the Contacts app stopped working properly. When I tried reinstalling (with a full wipe), TWRP crashed and the device would bootloop, so, as usual, I redownloaded the zip (and verified checksums), and the exact same thing happened. As it turns out I can't install anything on the device, TWRP crashes on installation every time and the ROMs bootloop.
Observed hint: the installation always crashes on steps related to the boot image, regardless of bootloader version installed.
Steps taken: tried every available TWRP version (including unofficial ones), tried different bootloaders, tried different ROMs (Oreo and Pie), tried flashing with full wipe and dirty. The problem persists.
After the installation crash I sometimes get "E:Legacy property environment did not initialize successfully. Properties will not be detected.". Subsequent attempt results in Aroma claiming the ROM is for greatlte and current device is "" and stopping immediately.
backup/restore in TWRP works fine which turned out to be my saving grace.
Enclosed are TWRP logs including a large last_log from /cache/recovery and a screenshot of current system version (but the problem persists on every bootloader/system configuration). I went through them, but couldn't find anything relevant, so any help will be greatly appreciated. I might be just dim and missing something obvious.
Click to expand...
Click to collapse
Some solutions:
> Firmware reset via Odin. There's a few guides on how to do that, it should fix your issues.
> If you get into TWRP, wipe your directories, mainly ones like /data, and reboot back to TWRP. Not system.
> Try a different rom/zip.
> Try older versions of TWRP if you can. TWRP is recovery.img, not boot.img, so it shouldn't be crashing unless you bonked up recovery.img. You could try flashing the stock one, or flash stock via odin again.
Hello everyone,
I recently wanted to root my galaxy tab s2 and install a custom rom on it to enhance performance, someting i've done before with my old phone where everything worked fine. So i used autoroot to root the tablet which worked fine and choose to install lineageos afterwards. i found a fitting version of lineage on their official website, installed twrp on my tablet and used it to install lineageos and GApps. However i did not unlock my bootloader using adb since i didnt have to do that back when i rooted my phone and i read on a forum that unlocking oem in the developer settings would be enough. This is where the problems start. After i installed the custom rom the tablet would try to boot into the os for a couple of minutes only showing a loading animation just to boot straight into recovery mode afterwards. In an attempt to fix the error i used odin to install a stock rom from sammobile on the tablet. However now it doesnt even boot into recovery anymore. instead it only shows the stock rom loading animation until the battery emptys. Though i can enter download mode from that position and then cancel it in order to reboot the device which enables me to enter recovery mode. Does anyone have an idea how i could boot a normal os again or is the device hard bricked? The only idea i have left is trying to install a new os from an sd card.
I have the same issue. I installed unofficial lineageos 16 to exynos 2015 t810. I have newest odin and twrp. Im wondering if i need to install or unlock the bootloader to get past the logo loop then recovery bootup after 5 minutes. I followed clean tutorials.
Update: i found this to try.
Quote:
Originally Posted by -beluga-
Hi, first of all thanks for the ROM. Unfortunately I am unable to get my T710 running properly with today's packages (it ran 15.1 so far)
- lineage-16.0-20191009-UNOFFICIAL-gts28wifi.zip
- addonsu-16.0-arm-signed.zip
- open_gapps-arm-9.0-pico-20191009.zip (some with nano or stock)
I am doing a full clean install every time (over 10x so far) but only get it to boot using the ROM alone. Any mod, such as addonsu, gapps or even trwp app cause it to show the Lineage boot screen for quite a while until dropping back into TWRP. Since there is a virtually infinite amount of permutations which versions to try - can someone who is successfully installed 16.0 with Gapps on a T710 let me know their version combination please?
Thanks.
pico-20191009 is giving problems with the 1009 build on my T810 too. Pico-20191006 and Magisk 19.4 are doing the trick for me.
Don't know about other combinations
BTW, it's advised not to install the TWRP app as it is known for causing bootloops on this rom.
Don't know for sure, but wiping internal storage before installing rom might be useful too.