Hi all,
I am installing CM13 on a Samsung Galaxy S4 Mini LTE serranoltexx and I have an issue with Gapps.
The ROM installs fine but once I install Gapps I get a forced closed messages. I checked a few guides and they suggested that this was due to the application permissions on CM13 but when I check these they appear to be fine.
Under the application menu I can see that the apps which Gapps installs are grayed out, almost like they are installed on the SD card but the SD card is missing! I have tried a number of times to delete cache but no luck.
I am using opengapps. I just tried using CM12 with open gapps but I get the same exact issue, therefore I think this is an issue with Gapps.
Can anybody offer any advise on how to get this working?
Thanks,
c
You can try different gapps (pico, micro ...) or recovery. I'm using cwm recovery
GT-I9190 cihazımdan Tapatalk kullanılarak gönderildi
umuturunc said:
You can try different gapps (pico, micro ...) or recovery. I'm using cwm recovery
GT-I9190 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
I tried different Gapps packages but not different recovery. I am using TWRP, do you have a link to the CWM which you are using?
ceanth said:
I tried different Gapps packages but not different recovery. I am using TWRP, do you have a link to the CWM which you are using?
Click to expand...
Click to collapse
I'm using latest version(6.0.5.1) of cwm on my serrano3g.
Here is a thread for your serranoltex device. http://forum.xda-developers.com/showthread.php?t=2364980
Sorry for my bad english.
umuturunc said:
I'm using latest version(6.0.5.1) of cwm on my serrano3g.
Here is a thread for your serranoltex device. http://forum.xda-developers.com/showthread.php?t=2364980
Sorry for my bad english.
Click to expand...
Click to collapse
Hi,
After flashing CWM Gapps worked! I now have an issue where by if I try and update Cyanogenmod via the Cyanogenmod updates, the device reboots into recovery however it doesn't flash the update, recovery fails.
Can you advise which recovery I would need to install to be compatible with using OTA Cyanogenmod updates?
You can also flash updates manually. Don't need to outoflash ��
But if you want to OTA update you should use cyanogen recovery. https://download.cyanogenmod.org/?device=serranoltexx
You can see cyanogenmod recovery right of the cyanogenmod build.
GT-I9190 cihazımdan Tapatalk kullanılarak gönderildi
umuturunc said:
You can also flash updates manually. Don't need to outoflash ��
But if you want to OTA update you should use cyanogen recovery. https://download.cyanogenmod.org/?device=serranoltexx
You can see cyanogenmod recovery right of the cyanogenmod build.
GT-I9190 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
The solution work?
Here's what worked for me.
First of all, I'm using TWRP 2.8. The root tutorial I followed gave me CWM so I switched my self. After that I tried installing gapps and I ran into the setup wizard and google app force closures. What seemed to have worked for me was to flash the ROM again which I downloaded through CM updates (it goes to the folder 'cmupdater' in your internal storage), boot, enable dev options, turn on advanced power menu, reboot to recovery through powr menu, install gapps micro and then reboot WITHOUT wiping dalvik/cache. I hope this helps some of you guys as it is what worked for me. It's sounds like alot but its the exact steps I followed.
---------- Post added at 10:45 PM ---------- Previous post was at 10:40 PM ----------
ceanth said:
Hi,
After flashing CWM Gapps worked! I now have an issue where by if I try and update Cyanogenmod via the Cyanogenmod updates, the device reboots into recovery however it doesn't flash the update, recovery fails.
Can you advise which recovery I would need to install to be compatible with using OTA Cyanogenmod updates?
Click to expand...
Click to collapse
Flash manually thought TWRP/CWM(TWRP recommended) . the ROM is saved in internal storage in a folder called 'cmupdater'.
Related
Please help!
After upgrading to twrp 2.6.3.1, then
wiping cache/data/Dalvik, then
format data, then
installing OMNI 4.4 + supersu + gapps....the ROM works fine but i have NO BASEBAND!
HELP!
tdaniels17 said:
Please help!
After upgrading to twrp 2.6.3.1, then
wiping cache/data/Dalvik, then
format data, then
installing OMNI 4.4 + supersu + gapps....the ROM works fine but i have NO BASEBAND!
HELP!
Click to expand...
Click to collapse
I had the identical issue with the CM11 4.4 Rom that willl03 put together. The issue with that one is TWRP.
I'm guessing TWRP is the most recent version available, yes? Have you tried CWM?
InertiaticFlow said:
I had the identical issue with the CM11 4.4 Rom that willl03 put together. The issue with that one is TWRP.
I'm guessing TWRP is the most recent version available, yes? Have you tried CWM?
Click to expand...
Click to collapse
Yes, and Yes.
Flash the latest CWM recovery ...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
gregsarg said:
Flash the latest CWM recovery ...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Tried with latest cwm already with the same results.
I also formatted complete drive when trying with cwm as well. No baseband still.
tdaniels17 said:
Tried with latest cwm already with the same results.
I also formatted complete drive when trying with cwm as well. No baseband still.
Click to expand...
Click to collapse
Did u flash it from rom manager app? I did it that way. Not the touch version. The classic style. I did that and all is fine
softballjunkee13 said:
Did u flash it from rom manager app? I did it that way. Not the touch version. The classic style. I did that and all is fine
Click to expand...
Click to collapse
Sure did. Still not working
cant update
softballjunkee13 said:
Did u flash it from rom manager app? I did it that way. Not the touch version. The classic style. I did that and all is fine
Click to expand...
Click to collapse
tdaniels17 said:
Sure did. Still not working
Click to expand...
Click to collapse
Happening to me also.
Not able to update to latest 2.6.3.1. it keeps failing. Rom Pro successfully updated to 2.6.3.0.
I downloaded the lastest recovery image from here: http://www.clockworkmod.com/rommanager (because the rom manager app was not installing the latest ewr 6.04.3 for me it kept installing 6.0.4.1 ,
Then uses this app (https://play.google.com/store/apps/d....recoverytools) to install the .img file (open app and choose the recovery you want to install [.img file on your sdcard].
note:
click on "flash other recovery" and find the .img file you downloaded from the link i posted.
I had this happen to me on my Sprint Note 2.
I tried flashing from TWRP and it failed, after updating twrp to 2.6.3.1 it flashed but baseband, imie, network etc was wiped. I restored my previous nandroid, flashed clockwork, then omni and it's working now.. I really do like twrp, plus the Omi OTA updates seem to require it for incremental live updates. But I'm really hesitant to switch back until this is confirmed fixed.
Gapps not Installing
Hi,
I installed custom rom nAOSProm_b26 with TWRP 2.8.5 on my Xperia S LT26i and now am having a problem.
The problem is that its not showing Play Store. I searched and found maybe its due to Gapps. I tried many packages of Gapps.zip but not successful. Also its saying the kernel does not have support SELINUX in start.
Please Help me in this regard will be very thankful as am new to this field and don't know much about this
Thanking in Advance...!!!
haris05 said:
Hi,
I installed custom rom nAOSProm_b26 with TWRP 2.8.5 on my Xperia S LT26i and now am having a problem.
The problem is that its not showing Play Store. I searched and found maybe its due to Gapps. I tried many packages of Gapps.zip but not successful. Also its saying the kernel does not have support SELINUX in start.
Please Help me in this regard will be very thankful as am new to this field and don't know much about this
Thanking in Advance...!!!
Click to expand...
Click to collapse
You need to flash gapps after flashing a ROM. Since You are on nAOSP b26, Your android version is 5.1 . Search for gapps package which works with 5.1 and the flash them via recovery. Also as for Your error, I would recommend a clean flash by following the instructions by the developer.
Mirhawk said:
You need to flash gapps after flashing a ROM. Since You are on nAOSP b26, Your android version is 5.1 . Search for gapps package which works with 5.1 and the flash them via recovery. Also as for Your error, I would recommend a clean flash by following the instructions by the developer.
Click to expand...
Click to collapse
I download Gapps for 5.1 but issue is I can install nAOSProm_b26 using TWRP 2.8.5 but cannot install it using TWRP 2.8.7.
On other hand I can install Gapps usinng TWRP 2.8.7 but cannot install it using TWRP 2.8.5
So many complex things are going on with me
One more thing I want to know that what do you mean by flash it via recovery. Is it boot.img in the ROM.zip file?
I followed the instructions but each time I failed Do not know why
Can you please help me further in this regard?
You have to say clearly step by step what you have did to flash the ROM or gapps.then only some1 can help you
same problem here!
i can flash gapps but the problem is after the boot and android upgrade all google apps pop up for unfortunately stopped and setup wizard also..
haris05 said:
I download Gapps for 5.1 but issue is I can install nAOSProm_b26 using TWRP 2.8.5 but cannot install it using TWRP 2.8.7.
On other hand I can install Gapps usinng TWRP 2.8.7 but cannot install it using TWRP 2.8.5
So many complex things are going on with me
One more thing I want to know that what do you mean by flash it via recovery. Is it boot.img in the ROM.zip file?
I followed the instructions but each time I failed Do not know why
Can you please help me further in this regard?
Click to expand...
Click to collapse
See, b25 onwards different mode has been followed in the nAOSP ROM. For that, You need to flash the recovery from the ROM.zip. Then flash the boot.img from the b26 zip via bootloader, and then flash the ROM. Are You following this sequence?
Also it doesn't matter what TWRP version You are using to flash gapps. You can always change the TWRP version. So flash the the TWRP with which ever TWRP version it gets flashed with, then change the TWRP if You want to, and then flash the gapps.
Flash it via recovery means flash it via TWRP. TWRP, CWM, Philz, these all are recoveries used to flash flashable zips via it.
The one You took example of, boot.img, is generally the kernel, which needs to be flashed via bootloader mode.
Also, I would recommend these gapps, they always worked for Me.
bojz said:
same problem here!
i can flash gapps but the problem is after the boot and android upgrade all google apps pop up for unfortunately stopped and setup wizard also..
Click to expand...
Click to collapse
Try the gapps I linked above.
Mirhawk is always a life saver for all new Comer's.
Mirhawk said:
Try the gapps I linked above.
Click to expand...
Click to collapse
thanks but still got no luck
nageswarswain said:
Mirhawk is always a life saver for all new Comer's.
Click to expand...
Click to collapse
Just helping out in whatever I can.
bojz said:
thanks but still got no luck
Click to expand...
Click to collapse
That is weird, Can You tell what problem You are facing? Mention the error text if You can. Also, You can try these TK Gapps.
Mirhawk said:
That is weird, Can You tell what problem You are facing? Mention the error text if You can. Also, You can try these TK Gapps.
Click to expand...
Click to collapse
already tried tha gapps also still the samw problem.
all google application was error popping out "unfortunately (google maps, google+ ,etc..) has stopped
then i already reset it in the (setting-application-all) but the setup wizard was not fixed and still popping out and i cannot get on the home screen.
bojz said:
already tried tha gapps also still the samw problem.
all google application was error popping out "unfortunately (google maps, google+ ,etc..) has stopped
then i already reset it in the (setting-application-all) but the setup wizard was not fixed and still popping out and i cannot get on the home screen.
Click to expand...
Click to collapse
Have u followed the procedure I sent you by message
Mirhawk said:
See, b25 onwards different mode has been followed in the nAOSP ROM. For that, You need to flash the recovery from the ROM.zip. Then flash the boot.img from the b26 zip via bootloader, and then flash the ROM. Are You following this sequence?
Also it doesn't matter what TWRP version You are using to flash gapps. You can always change the TWRP version. So flash the the TWRP with which ever TWRP version it gets flashed with, then change the TWRP if You want to, and then flash the gapps.
Flash it via recovery means flash it via TWRP. TWRP, CWM, Philz, these all are recoveries used to flash flashable zips via it.
The one You took example of, boot.img, is generally the kernel, which needs to be flashed via bootloader mode.
Also, I would recommend these gapps, they always worked for Me.
Try the gapps I linked above.
Click to expand...
Click to collapse
I guess am skipping one step of recovery.... gonna try that.
I did flash by using recovery and now I am successful in installing gapps using TWRP 2.8.5.
Now the other issue am facing and that is of unknown IMEI
after flashing 4-5 times the issue resolved but now am facing issue "Unfortunately Setup Wizard has stopped" and it is not letting me do anything with my phone
Any Suggestion what should I do now
bojz said:
same problem here!
i can flash gapps but the problem is after the boot and android upgrade all google apps pop up for unfortunately stopped and setup wizard also..
Click to expand...
Click to collapse
exactly the same problem I am facing
bojz said:
already tried tha gapps also still the samw problem.
all google application was error popping out "unfortunately (google maps, google+ ,etc..) has stopped
then i already reset it in the (setting-application-all) but the setup wizard was not fixed and still popping out and i cannot get on the home screen.
Click to expand...
Click to collapse
The same thing exactly
Got Any solution to that?
haris05 said:
The same thing exactly
Got Any solution to that?
Click to expand...
Click to collapse
Can You use the b25b version? It is what I'm on now and it works just fine for Me. There are no major updates in b26 as it is.
only in this nAOSP b26 rom im facing this problem "system wizard has stopped" after installing gapps. but i tried other rom then i dont have any problem.
Mirhawk said:
Can You use the b25b version? It is what I'm on now and it works just fine for Me. There are no major updates in b26 as it is.
Click to expand...
Click to collapse
Let me try this now
Mirhawk said:
Can You use the b25b version? It is what I'm on now and it works just fine for Me. There are no major updates in b26 as it is.
Click to expand...
Click to collapse
Cannot flash using this ROM. Its giving error on installing
These Steps am Following:
1) Connected Phone on flashboot mode (By Pressing VolUp+Power Key and connecting the cable and it shows blue LED)
2) Flashed with recovery.img file in nAOSProm_b26 using flashtool (Fastboot mode)
3) Flashed with boot.img file in nAOSProm_b26 using flashtool (Fastboot mode)
4) flashed with TWRP 2.8.5 using flashtool (Fastboot mode)
5) disconnected cable and open bootloader then flashed using nAOSProm.zip file
6) wipe cache and dalvik (also treid by wiping cache/dalvik/data and other option I forgot (total 4))
7) flashed using pa_Gapps (as only this Gapps are flashed on my phone, others are giving errors)
same I followed for b25b but its giving error on 5th step mentioned above.
So what wrong am doing
I decided not to update to 3.2.8 after reading all the bad reviews. Now that 4.0.2 is out and reviews are not so bad, im going to update to 4.0.2. I'm on OxygenOS 3.2.7 and the official OTA update installer is showing the message " Rooted device detected,update may fail."
After reading some posts about OTA updates failing for rooted users and causing loops, I manually downloaded 4.0.2 from here
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_4.0.2/
Can someone please tell how to proceed now. ( Device is rooted, twrp and xposed installed )
Can i flash the downloaded update from TWRP ? can someone please give steps to update.
Thanks
just do a clean flash like any other rom. flash super su immediately after the rom without rebooting to get root access.
jaj473 said:
I decided not to update to 3.2.8 after reading all the bad reviews. Now that 4.0.2 is out and reviews are not so bad, im going to update to 4.0.2. I'm on OxygenOS 3.2.7 and the official OTA update installer is showing the message " Rooted device detected,update may fail."
After reading some posts about OTA updates failing for rooted users and causing loops, I manually downloaded 4.0.2 from here
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_4.0.2/
Can someone please tell how to proceed now. ( Device is rooted, twrp and xposed installed )
Can i flash the downloaded update from TWRP ? can someone please give steps to update.
Thanks
Click to expand...
Click to collapse
I think the safest method is the following :
1. Make a copy of the Internal memory contents so that you can recover it at the end.
2. Reboot Fastboot and flash stock recovery by adb.
3. Reboot recovery and make full wipes from stock recovery (factory reset, cache and internal memory). At this point, data partition will have change to f2fs format.
4. Put the full 4.0.2 rom inside adb folder, reboot to Fastboot and connect the device to the computer again.
5. Install the rom and when it finishs, reboot system. When the rom is showed in the screen, reboot to Fastboot again and install the last official TWRP by adb again.
6. Reboot recovery, connect it to the pc and copy Supersu to the internal memory.
7. Switch it off from the pc, install Supersu from recovery and reboot system.
8. Copy the saved contents to the internal SD.
That's all...
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Crazyhat said:
I think the safest method is the following :
1. Make a copy of the Internal memory contents so that you can recover it at the end.
2. Reboot Fastboot and flash stock recovery by adb.
3. Reboot recovery and make full wipes from stock recovery (factory reset, cache and internal memory). At this point, data partition will have change to f2fs format.
4. Put the full 4.0.2 rom inside adb folder, reboot to Fastboot and connect the device to the computer again.
5. Install the rom and when it finishs, reboot system. When the rom is showed in the screen, reboot to Fastboot again and install the last official TWRP by adb again.
6. Reboot recovery, connect it to the pc and copy Supersu to the internal memory.
7. Switch it off from the pc, install Supersu from recovery and reboot system.
8. Copy the saved contents to the internal SD.
That's all...
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Click to expand...
Click to collapse
Why would you want to sideload the ROM and then perform a wipe to get f2fs, also with the stock recovery. It can be done via twrp itself and the ROM can be flashed normally via twrp.
Sent from my OnePlus3 using XDA Labs
bonham1988 said:
Why would you want to sideload the ROM and then perform a wipe to get f2fs, also with the stock recovery. It can be done via twrp itself and the ROM can be flashed normally via twrp.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
I said this is the safest way to avoid the dm-verity message. Theoretically, what you propose is correct but it's not as safer. In fact, this forum is plenty of issues from people who tried to do it like you say.
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Crazyhat said:
I said this is the safest way to avoid the dm-verity message. Theoretically, what you propose is correct but it's not as safer. In fact, this forum is plenty of issues from people who tried to do it like you say.
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Click to expand...
Click to collapse
No there are no issues with it apart from the DM verity splash screen. If you doing a clean install you should not have any issue and if DM verity is such a big deal you can also flash 3.2.8 or 3.5.5 forward to get rid of it.
Sent from my OnePlus3 using XDA Labs
jaj473 said:
I decided not to update to 3.2.8 after reading all the bad reviews. Now that 4.0.2 is out and reviews are not so bad, im going to update to 4.0.2. I'm on OxygenOS 3.2.7 and the official OTA update installer is showing the message " Rooted device detected,update may fail."
After reading some posts about OTA updates failing for rooted users and causing loops, I manually downloaded 4.0.2 from here
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_4.0.2/
Can someone please tell how to proceed now. ( Device is rooted, twrp and xposed installed )
Can i flash the downloaded update from TWRP ? can someone please give steps to update.
Thanks
Click to expand...
Click to collapse
Consider one Thing: There is no xposed available so far. That's why I stay with 3.2.8.
---------- Post added at 12:44 PM ---------- Previous post was at 12:38 PM ----------
Crazyhat said:
I think the safest method is the following :
1. Make a copy of the Internal memory contents so that you can recover it at the end.
2. Reboot Fastboot and flash stock recovery by adb.
3. Reboot recovery and make full wipes from stock recovery (factory reset, cache and internal memory). At this point, data partition will have change to f2fs format.
4. Put the full 4.0.2 rom inside adb folder, reboot to Fastboot and connect the device to the computer again.
5. Install the rom and when it finishs, reboot system. When the rom is showed in the screen, reboot to Fastboot again and install the last official TWRP by adb again.
6. Reboot recovery, connect it to the pc and copy Supersu to the internal memory.
7. Switch it off from the pc, install Supersu from recovery and reboot system.
8. Copy the saved contents to the internal SD.
That's all...
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Click to expand...
Click to collapse
One question to your procedure:
Which version of stock recovery do you use in this procedure? Since you make a full wipe before installing anything else to f2fs I assume, it must be the latest version. Do you have a download link to this for safety reasons? Tks a lot!
bonham1988 said:
No there are no issues with it apart from the DM verity splash screen. If you doing a clean install you should not have any issue and if DM verity is such a big deal you can also flash 3.2.8 or 3.5.5 forward to get rid of it.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Dm-verity is a problem for many people. I won't need to go back to 3.2.8 rom again if previously I did it well so, in my modest opinion, it's much better to ensure that it doesn't happen. Anyway, you can do it whatever you like. It's not my business.
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Crazyhat said:
Dm-verity is a problem for many people. I won't need to go back to 3.2.8 rom again if previously I did it well so, in my modest opinion, it's much better to ensure that it doesn't happen. Anyway, you can do it whatever you like. It's not my business.
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Click to expand...
Click to collapse
You don't actually have to go to 3.2.8 ROM. You just have to flash the firmware and modem. And DM verity is subjective there are many people myself included who don't find that extra splash screen an issue at all.
Sent from my OnePlus3 using XDA Labs
Sir Backe said:
Consider one Thing: There is no xposed available so far. That's why I stay with 3.2.8.
---------- Post added at 12:44 PM ---------- Previous post was at 12:38 PM ----------
One question to your procedure:
Which version of stock recovery do you use in this procedure? Since you make a full wipe before installing anything else to f2fs I assume, it must be the latest version. Do you have a download link to this for safety reasons? Tks a lot!
Click to expand...
Click to collapse
The safest place for that is the OnePlus site. You have to flash v2 which is the latest version. The OnePlus site will merely show you one link without indicating whether it is for v1 or v2. You can go ahead and download it as it is the v2.
bonham1988 said:
You don't actually have to go to 3.2.8 ROM. You just have to flash the firmware and modem. And DM verity is subjective there are many people myself included who don't find that extra splash screen an issue at all.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Ok, great! I have been several months with it too, but only because It never was a trouble for me neither.
---------- Post added at 02:29 PM ---------- Previous post was at 02:13 PM ----------
Sir Backe said:
Consider one Thing: There is no xposed available so far. That's why I stay with 3.2.8.
---------- Post added at 12:44 PM ---------- Previous post was at 12:38 PM ----------
One question to your procedure:
Which version of stock recovery do you use in this procedure? Since you make a full wipe before installing anything else to f2fs I assume, it must be the latest version. Do you have a download link to this for safety reasons? Tks a lot!
Click to expand...
Click to collapse
Probably, this is not the last version, but it works fine. Right now I'm working and I hope you'll understand that I don't have enough time to look for the last version. Anyway, I leave you this link just in case it is useful for you....
https://s3.amazonaws.com/oxygenos.oneplus.net/recovery.img
@Crazyhat
Tks for the link. I just downloaded it from the Oneplus Website according to @tnsmani recommendation. I didn't actually know that it is there, hidden in the depth of the OP Website mess .
Sir Backe said:
@Crazyhat
Tks for the link. I just downloaded it from the Oneplus Website according to @tnsmani recommendation. I didn't actually know that it is there, hidden in the depth of the OP Website mess .
Click to expand...
Click to collapse
Hahaha.... You will have to trust them [emoji4] [emoji106]
Enviado desde mi ONEPLUS A3003 mediante Tapatalk
Im using a custom rom installed via twrp,
I wanna go back to miui, will it be fine if clean flashed over the current custom ROM through twrp, or do i need to follow any other way?
Try use ROM xiaomi.eu
---------- Post added at 01:00 AM ---------- Previous post was at 01:00 AM ----------
Or mi-globe.com
jaspad1710 said:
Im using a custom rom installed via twrp,
I wanna go back to miui, will it be fine if clean flashed over the current custom ROM through twrp, or do i need to follow any other way?
Click to expand...
Click to collapse
Its easy..
Clean flash ur MIUI rom... (Using TWRP)
And use lazyflasher to skip dm-verity check..
Here : https://drive.google.com/file/d/0ByWEieei-0nyMTR4R0dxWk9BTms/view?usp=sharing
Done .... Reboot and Enjoy !!
QwertySDuos2 said:
Its easy..
Clean flash ur MIUI rom... (Using TWRP)
And use lazyflasher to skip dm-verity check..
Here : https://drive.google.com/file/d/0ByWEieei-0nyMTR4R0dxWk9BTms/view?usp=sharing
Done .... Reboot and Enjoy !!
Click to expand...
Click to collapse
Wait, i installed miui9 correct version from miui website, i properly did a clean flash (installed correct openg) which im 100% sure, but the phone was stuck at boot logo, but twrp was working with the hardware key combo..pls help
And a peculiar thing is i have been using openg full arm64
Since i first begun using los unofficial, but today after flashing miui its showing that mine is arm and not arm64..pls give ur valuable insights
jaspad1710 said:
Wait, i installed miui9 correct version from miui website, i properly did a clean flash (installed correct openg) which im 100% sure, but the phone was stuck at boot logo, but twrp was working with the hardware key combo..pls help
And a peculiar thing is i have been using openg full arm64
Since i first begun using los unofficial, but today after flashing miui its showing that mine is arm and not arm64..pls give ur valuable insights
Click to expand...
Click to collapse
Format data and cache partitions as ext4 not as f2fs..
Then follow my instructions as before..
Miui has inbuilt gapps..
Why u need opengapps then ??
(Dont flash gapps on miui..)
QwertySDuos2 said:
Format data and cache partitions as ext4 not as f2fs..
Then follow my instructions as before..
Miui has inbuilt gapps..
Why u need opengapps then ??
(Dont flash gapps on miui..)
Click to expand...
Click to collapse
Holyy so flashing the gapps crashed it?
jaspad1710 said:
Holyy so flashing the gapps crashed it?
Click to expand...
Click to collapse
Yeah... Probably coz the gapps in miui are in data partition instead of system partiton (atleast that was the case with miui 8 on my other device the Redmi Note 4G)
TWRP 3.4 for Android 10 SM-T83x
This build of TWRP is now Official.
Official TWRP web link
Built using OMNI source
TWRP v3.4
See post #2 for install steps
Changelog...
1.0
Initial build
MTP, OTG and SDcard all working
4.0
Now in portrait mode
Brightness fixed
5.0
Updated for Android 10
TWRP Downloads
Download folder
Official device tree on twrp.me
--------------------->
Kernel Source
Source
Device Tree
Source
--------------------->
Beer fund
You can flash TWRP two ways, either directly from an existing TWRP install, using the linked TWRP.img file. Or you can flash using Odin and the TWRP.tar file.
You will need a custom kernel with dm-verity disabled to be able to boot up afterwards. You will also need to disable encryption and format data to be able to read from the sdcard (encryption isn't supported).
The flashing process is as follows.
Get yourself onto stock Pie firmware, using Odin to flash the complete package. Before proceeding. Boot up and make sure you have OEM unlock switch and its activated.
1. Boot into Download mode and Flash TWRP (Download) using Odin (use AP)
2. Immediately boot into TWRP after flashing takes place, hold vol up and power.
3. Format data partition (wipe/format data)
4. Reboot recovery
5. Copy WETA Kernel + Encryption disabler + Magisk zip to device. - (Download Kernel - Encryption disabler)
6. Flash WETA Kernel + Encrypt disabler + Magisk zip.
7. Boot up system, if it hangs on Samsung logo after 3min perform hard reboot.
8. Connect to internet and go to dev settings and check oem unlock is present before any rebooting.
** Custom kernel is universal for all bootloader v4 firmware.
--->
problem download
From croatia I cannot access this link. Can you upload on mega.
Thanks
macakfelix said:
From croatia I cannot access this link. Can you upload on mega.
Thanks
Click to expand...
Click to collapse
Your kidding? Usually people say upload anywhere but mega because of access.. haha. But sure. I'll mirror it to mega
Sent from my SM-N9600 using Tapatalk
macakfelix said:
From croatia I cannot access this link. Can you upload on mega.
Thanks
Click to expand...
Click to collapse
Mega mirrors are up,
Sent from my SM-N9600 using Tapatalk
Tested and working on T835 Pie. Finally good to have a TWRP with MTP & adb working. Thanks mate.
Mentalmuso said:
TWRP 3.3.0 for PIE SM-T83x
--------------------->
Beer fund
Click to expand...
Click to collapse
Hi friend, i flashed with odin but seems not to work, same as without flashing... im on pie now, but when on oreo was not so easy to flash twrp as this... i remember had to flash 1 or 2 more files, but not sure... any help?
EDIT im talking about TabS4_oreo_forced_encryption_disabler... do you get it work just flashing twrp or do you need any extra procedure?
Thanks in advance
My device is a SM-T835N
wallyhenderson said:
Hi friend, i flashed with odin but seems not to work, same as without flashing... im on pie now, but when on oreo was not so easy to flash twrp as this... i remember had to flash 1 or 2 more files, but not sure... any help?
EDIT im talking about TabS4_oreo_forced_encryption_disabler... do you get it work just flashing twrp or do you need any extra procedure?
Thanks in advance
My device is a SM-T835N
Click to expand...
Click to collapse
Sorry, I completely forgot that
Flash TWRP with Odin
Reboot straight to twrp.
Flash encryption disabler.
Format data.
Reboot recovery.
Mount data make sure you can read it .
Then you can flash a rom, kernel etc. I'll update the op in a bit
Sent from my SM-N9600 using Tapatalk
macakfelix said:
From croatia I cannot access this link. Can you upload on mega.
Thanks
Click to expand...
Click to collapse
https://mega.nz/#F!TZNgRYyB!7wa-W3moNILsezgkuj3nKA
Mentalmuso said:
Sorry, I completely forgot that
Flash TWRP with Odin
Reboot straight to twrp.
Flash encryption disabler.
Format data.
Reboot recovery.
Mount data make sure you can read it .
Then you can flash a rom, kernel etc. I'll update the op in a bit
Sent from my SM-N9600 using Tapatalk
Click to expand...
Click to collapse
Friend i have
Flash "TWRP-ODIN_Pie_3.3.0_sm-t83x_mentalmuso.tar" with Odin OK
Reboot straight to twrp OK
Flash encryption disabler "T83x_PIE_encrypt_disabler_+++.zip" OK
Format data OK
Reboot recovery OK
Mount data make sure you can read it OK (think ok, didnt know what to do)
And now im in a loop boot... can you help me i use phone to work and sadly will have to solve today or have to flash stock pie rom
Thanks in advance
Restored stock pie rom... seems to work fine without twrp but when trying to flash TWRP-ODIN_Pie_3.3.0_sm-t83x_mentalmuso and it says "only official released binaries allowed to be flashed (recovery)
wallyhenderson said:
Friend i have
Flash "TWRP-ODIN_Pie_3.3.0_sm-t83x_mentalmuso.tar" with Odin OK
Reboot straight to twrp OK
Flash encryption disabler "T83x_PIE_encrypt_disabler_+++.zip" OK
Format data OK
Reboot recovery OK
Mount data make sure you can read it OK (think ok, didnt know what to do)
And now im in a loop boot... can you help me i use phone to work and sadly will have to solve today or have to flash stock pie rom
Thanks in advance
Click to expand...
Click to collapse
What version of Android are you on?
Sent from my SM-N9600 using Tapatalk
wallyhenderson said:
Friend i have
Flash "TWRP-ODIN_Pie_3.3.0_sm-t83x_mentalmuso.tar" with Odin OK
Reboot straight to twrp OK
Flash encryption disabler "T83x_PIE_encrypt_disabler_+++.zip" OK
Format data OK
Reboot recovery OK
Mount data make sure you can read it OK (think ok, didnt know what to do)
And now im in a loop boot... can you help me i use phone to work and sadly will have to solve today or have to flash stock pie rom
Thanks in advance
Click to expand...
Click to collapse
Have you flashed a custom kernel? Or at least flashed magisk?
You cant boot using a stock kernel, when you have any other custom features on your device.
Sent from my SM-N9600 using Tapatalk
Mentalmuso said:
Have you flashed a custom kernel? Or at least flashed magisk?
Sent from my SM-N9600 using Tapatalk
Click to expand...
Click to collapse
it is mandatory to flash a custom kernel? will do if nessesary... i didnt... and didnt flashed magisk
---------- Post added at 11:05 PM ---------- Previous post was at 10:57 PM ----------
Mentalmuso said:
What version of Android are you on?
Sent from my SM-N9600 using Tapatalk
Click to expand...
Click to collapse
im on pie T835NKOU2BSD1
wallyhenderson said:
it is mandatory to flash a custom kernel? will do if nessesary... i didnt... and didnt flashed magisk
---------- Post added at 11:05 PM ---------- Previous post was at 10:57 PM ----------
im on pie T835NKOU2BSD1
Click to expand...
Click to collapse
Kernel - pre rooted should boot. https://nextcloud.justbeca.us/s/JMgdcpt6kxdwNzo
Sent from my SM-T830 using Tapatalk
What are the steps for flashing the twrp 3.3.0 img via an existing twrp install?
hpc305 said:
What are the steps for flashing the twrp 3.3.0 img via an existing twrp install?
Click to expand...
Click to collapse
install - img - select the img file - select recovery
Sent from my SM-N9600 using Tapatalk
Encryption Disabler was broken
Updated to V2, please use this or there will be problems.
See post #2 for downloads.
--->
Mentalmuso said:
You can flash TWRP two ways, either directly from an existing TWRP install, using the linked TWRP.img file. Or you can flash using Odin and the TWRP.tar file.
You will need a custom kernel with dm-verity disabled to be able to boot up afterwards. You will also need to disable encryption and format data to be able to read from the sdcard (encryption isn't supported).
The flashing process is as follows.
Get yourself onto stock Pie firmware, using Odin to flash the complete package. Before proceeding. Boot up and make sure you have OEM unlock switch and its activated.
1. Boot into Download mode and Flash TWRP (Download) using Odin
2. Immediately boot into TWRP after flashing takes place, hold vol up and power.
3. Format data partition (wipe/format data)
4. Reboot recovery
5. Copy Encryption disabler and WETA_Kernel or WETA_Rom to device - (Download Enryption disabler) (Download WETA_Kernel)
6. Flash Encryption disabler, Flash WETA_Kernel or WETA_Rom
7. Boot up system, if it hangs on Samsung logo after 3min perform hard reboot.
8. Connect to internet and go to dev settings and cheeck oem unlock is present before any rebooting.
**Custom kernel is pre-rooted with magisk.
**You will need to manually install magisk manager app.
--->
Click to expand...
Click to collapse
Some things to note:
0. Requirements are:
USB Cable (Samsung Tab S4 default cable recommended)
A computer where Odin works (ie. my AM4 X370 Ryzen 7 system did not work, maybe some driver issue?)
Best is to put encryption disabler & Kernel onto the micro SD card in the Tab S4 already, you can flash from SD card in TWRP!
1. Flash TWRP in AP slot - beware if you did not untick Auto Reboot, it will immediately restart and you miss 2.
2. Hold those buttons before the vibration kicks in, otherwise you are too late
4. I couldn't do that from TWRP itself for some reason (it just shut off), but button combo worked perfectly
5. [Edit] Do that before hand, I recommend the micro SD card you can put into the Tab S4
6. I flashed encryption disabler (V2) first, then you have to flash the kernel image, flash it to BOOT!
7. Don't just wait 3 min, my Tablet booted after 10 min without issue! I had this before aswell, you just need to give it more time!
Question: Can I update Magisk with this?
neuer31 said:
Some things to note:
0. Requirements are:
USB Cable (Samsung Tab S4 default cable recommended)
A computer where Odin works (ie. my AM4 X370 Ryzen 7 system did not work, maybe some driver issue?)
Best is to put encryption disabler & Kernel onto the micro SD card in the Tab S4 already, you can flash from SD card in TWRP!
1. Flash TWRP in AP slot - beware if you did not untick Auto Reboot, it will immediately restart and you miss 2.
2. Hold those buttons before the vibration kicks in, otherwise you are too late
4. I couldn't do that from TWRP itself for some reason (it just shut off), but button combo worked perfectly
6. I flashed encryption disabler (V2) first, then you have to flash the kernel image, flash it to BOOT!
7. Don't just wait 3 min, my Tablet booted after 10 min without issue! I had this before aswell, you just need to give it more time!
Question: Can I update Magisk with this?
Click to expand...
Click to collapse
Yeah flashing magisk should be fine once your data partition is unencrypted.
Sent from my SM-N9600 using Tapatalk
Mentalmuso said:
install - img - select the img file - select recovery
Sent from my SM-N9600 using Tapatalk
Click to expand...
Click to collapse
F###, thanks, bro.
Just flashed it as recovery and have this now.
Can you delete this suggestion? It should be flashed as Boot, GOD!