Related
Marshmallow for this device, keeps crashing as it is (com.android.phone, RIL). Getting the problem solved is easy, @puntoazul already written something like that, but I managed to get everything that has to be flashed in a single post.
Flash these files, in the next order, from top to bottom:
- A-GAPPS_6.0.1_09022016.zip - https://mega.nz/#!M99xiQbZ!fcclA9QDSXxxizsifu21MUbgMGsyRsNCCHPO4KrF5xQ (thanks to @puntoazul for packing it)
- APNFixer4CM13.zip - http://forum.xda-developers.com/attachment.php?attachmentid=3689957&d=1458482477 (thanks to @puntoazul for packing it)
- UNIVERSAL NFC DESTROYER - http://forum.xda-developers.com/attachment.php?attachmentid=3280610&d=1429942749 (thanks to @-CALIBAN666- for developing it), yeah, it's made for lollipop but works perfectly.
- Media.zip (codecs pack) http://forum.xda-developers.com/attachment.php?attachmentid=3680746&d=1457817927 (thanks to @EdwinMoq for packing it.)
When you're done, do a factory reset and reboot your device. Then, enjoy Marshmallow .
EDIT: Media.zip seems to be a mistyped step, I haven't found it and it wasn't needed to get a successful startup on my device.
EDIT: It seems like it's needed, anyways, I haven't found it, waiting for @EdwinMoq to answer.
EDIT: Added Media.zip, found at http://forum.xda-developers.com/opt...ogenmod-13-t3303671/post65803228#post65803228 ( @EdwinMoq 's post).
facuarmo said:
Marshmallow for this device, keeps crashing as it is (com.android.phone, RIL). Getting the problem solved is easy, @puntoazul already written something like that, but I managed to get everything that has to be flashed in a single post.
Flash these files, in the next order, from top to bottom:
- A-GAPPS_6.0.1_09022016.zip - https://mega.nz/#!M99xiQbZ!fcclA9QDSXxxizsifu21MUbgMGsyRsNCCHPO4KrF5xQ (thanks to @puntoazul for packing it)
- APNFixer4CM13.zip - http://forum.xda-developers.com/attachment.php?attachmentid=3689957&d=1458482477 (thanks to @puntoazul for packing it)
- UNIVERSAL NFC DESTROYER - http://forum.xda-developers.com/attachment.php?attachmentid=3280610&d=1429942749 (thanks to @-CALIBAN666- for developing it), yeah, it's made for lollipop but works perfectly.
- Media.zip (codecs pack) http://forum.xda-developers.com/attachment.php?attachmentid=3680746&d=1457817927 (thanks to @EdwinMoq for packing it.)
When you're done, do a factory reset and reboot your device. Then, enjoy Marshmallow .
EDIT: Media.zip seems to be a mistyped step, I haven't found it and it wasn't needed to get a successful startup on my device.
EDIT: It seems like it's needed, anyways, I haven't found it, waiting for @EdwinMoq to answer.
EDIT: Added Media.zip, found at http://forum.xda-developers.com/opt...ogenmod-13-t3303671/post65803228#post65803228 ( @EdwinMoq 's post).
Click to expand...
Click to collapse
Ive been experiencing the same problems you have, but i found my own alternate way. Since this phone isnt my daily driver, i used lucky patcher to remove the phone services app aka com.android.phone from the system.Everything is fixed, all stabilized and smooth. I still get crashing from phone and messaging storage,but no lag or stability issues. But ill try this anyway to try to completely remedy the crashing
As only two entries for Orange seem to be missing in the APN database: Does everyone need that fix because the APN list is totally corrupted by this, or only certain Orange customers?
Elite.101 said:
Ive been experiencing the same problems you have, but i found my own alternate way. Since this phone isnt my daily driver, i used lucky patcher to remove the phone services app aka com.android.phone from the system.Everything is fixed, all stabilized and smooth. I still get crashing from phone and messaging storage,but no lag or stability issues. But ill try this anyway to try to completely remedy the crashing
Click to expand...
Click to collapse
Okay, please let me know what happened when you're done.
lecorbusier said:
As only two entries for Orange seem to be missing in the APN database: Does everyone need that fix because the APN list is totally corrupted by this, or only certain Orange customers?
Click to expand...
Click to collapse
For a better stability, you must flash it. For example, running this ROM without this patch, the RIL keeps crashing, taking in mind that Movistar and Tuenti (a lesser know Argentina provider, a recently started provider), are not being detected.
I'll wait for the next build. Then probably use it as a Wireless AP, as there are huge problems resulting from the small data partition and Ram. I still hope that MMs z-buffer feature provides some solution. This whole mess started about half a year ago and getting worse, on the L9 and a similarly featured tablet with CM11, so it's not the rom's fault. The tablet has plenty of space on the data partition, however, but ram and SoC face similar problems.
My current wireless AP is an Iphone 4s with only 0,5GB Ram. And it's is still working reliably, no apps freezing and fcing, and I can access websites which will make Firefox on the L9 and said tablet quit every time.
All the affected apps seem to deal with HTML code and are supposed to use the system webview engine. Updating the Google webview engine is possible with CM12.1 and 13, but to no avail, only taking space on the data partition.
facuarmo said:
Okay, please let me know what happened when you're done.
Click to expand...
Click to collapse
Well. I tried it. No crashing at all with A-Gapps or Gapps mini
But I kept getting kernel panics,even while charging.So I reverted to my system modified nandroid backup in which I uninstalled Phone services aka com.Android. phone and disabled Phone and messaging storage app.
Elite.101 said:
Well. I tried it. No crashing at all with A-Gapps or Gapps mini
But I kept getting kernel panics,even while charging.So I reverted to my system modified nandroid backup in which I uninstalled Phone services aka com.Android. phone and disabled Phone and messaging storage app.
Click to expand...
Click to collapse
Follow this http://forum.xda-developers.com/showpost.php?p=65892603&postcount=395
As i have previously explained in original thread all of these files in a single go. with order defined
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) If you have a p768 flash campatch
Also flashed NFC Destroyer so that on booting for the first time... i did'n encountered any error at all.. i have been using this ROM as my daily driver and never encountered any kernel panic or ant other error also i didn't faced any rotation problem. its working fine as it should be. Only thing i am concerned about is battery, it drains very fast, tweaking with kernel auditor didn't help me either. other then this i haven't faced any problem, everything is working fine, i'm able to install Xposed framework without any problem.. Great work......
I have also tried this with New TWRP Recovery.... worked like a charm
Elite.101 said:
Well. I tried it. No crashing at all with A-Gapps or Gapps mini
But I kept getting kernel panics,even while charging.So I reverted to my system modified nandroid backup in which I uninstalled Phone services aka com.Android. phone and disabled Phone and messaging storage app.
Click to expand...
Click to collapse
Can you tell me your real phone model? There're some hard incompatibilities between the P760 and the P769.
Codeplex said:
Follow this http://forum.xda-developers.com/showpost.php?p=65892603&postcount=395
As i have previously explained in original thread all of these files in a single go. with order defined
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) If you have a p768 flash campatch
Also flashed NFC Destroyer so that on booting for the first time... i did'n encountered any error at all.. i have been using this ROM as my daily driver and never encountered any kernel panic or ant other error also i didn't faced any rotation problem. its working fine as it should be. Only thing i am concerned about is battery, it drains very fast, tweaking with kernel auditor didn't help me either. other then this i haven't faced any problem, everything is working fine, i'm able to install Xposed framework without any problem.. Great work......
I have also tried this with New TWRP Recovery.... worked like a charm
Click to expand...
Click to collapse
Well, ill try this.The way i tried this was in a different order, but pretty much i have the phone under control since i uninstalled com.android.phone aka Phone Services and disabled Phone and messaging storage.
but i guess ill try this.i need the exact correct order with NFC Destroyer in the list in order of flashing.
---------- Post added at 01:31 PM ---------- Previous post was at 01:30 PM ----------
facuarmo said:
Can you tell me your real phone model? There're some hard incompatibilities between the P760 and the P769.
Click to expand...
Click to collapse
I currently Have the LG-P769. T-Mobile variant
Elite.101 said:
Well. I tried it. No crashing at all with A-Gapps or Gapps mini
But I kept getting kernel panics,even while charging.So I reverted to my system modified nandroid backup in which I uninstalled Phone services aka com.Android. phone and disabled Phone and messaging storage app.
Click to expand...
Click to collapse
Flash in this order (works for me every time)
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) NFC Destroyer
and reboot..
Codeplex said:
Flash in this order (works for me every time)
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) NFC Destroyer
and reboot..
Click to expand...
Click to collapse
Alright. Ill try this right now.Ima do a backup first.
Codeplex said:
Flash in this order (works for me every time)
1) Goto TWRP recovery can also use new TWRP 3.0.2.0 (i have already installed marshmallow without any errors)
2) Wipe system, Cache and Davic
3) Flash rom
4) Flash Media.zip
5) Flash A-GAPPS_6.0.1_09022016.zip
6) Flash APNFixer4CM13.zip
7) NFC Destroyer
and reboot..
Click to expand...
Click to collapse
im still having problems. i just finished setting up and now i have a kernel panic.......reverting now
Elite.101 said:
Well, ill try this.The way i tried this was in a different order, but pretty much i have the phone under control since i uninstalled com.android.phone aka Phone Services and disabled Phone and messaging storage.
but i guess ill try this.i need the exact correct order with NFC Destroyer in the list in order of flashing.
---------- Post added at 01:31 PM ---------- Previous post was at 01:30 PM ----------
I currently Have the LG-P769. T-Mobile variant
Click to expand...
Click to collapse
The kernel panics that you're experiencing, are also being faced by most of the people who has tried the P760 build in the P769, please check the ROM @EdwinMoq 's post and download the special build for this model, and try again. Then, please tell me how it goes.
facuarmo said:
The kernel panics that you're experiencing, are also being faced by most of the people who has tried the P760 build in the P769, please check the ROM @EdwinMoq 's post and download the special build for this model, and try again. Then, please tell me how it goes.
Click to expand...
Click to collapse
Well specifically, i used the p769 version. i tried apn fixer, nfc destroyer and media.zip, but the problem persisted. so i just reverted back to my nandroid backup in which i uninstalled com.android.phone aka phone services and disabled phone and messaging storage.I have it stable this way without kernel panics and using gapps mini since this isnt my daily driver. My galaxy core prime is SMG360T1.
Elite.101 said:
Well specifically, i used the p769 version. i tried apn fixer, nfc destroyer and media.zip, but the problem persisted. so i just reverted back to my nandroid backup in which i uninstalled com.android.phone aka phone services and disabled phone and messaging storage.I have it stable this way without kernel panics and using gapps mini since this isnt my daily driver. My galaxy core prime is SMG360T1.
Click to expand...
Click to collapse
Hmmm... Idk, sorry. That's what I've learned from here, not much atm haha.
facuarmo said:
Hmmm... Idk, sorry. That's what I've learned from here, not much atm haha.
Click to expand...
Click to collapse
True.one thing I want fixed is the headphones problem where sound goes to speaker
Elite.101 said:
True.one thing I want fixed is the headphones problem where sound goes to speaker
Click to expand...
Click to collapse
That's quite strange, seems like a bad kernel. For me, using the P760 (in the P778g, Argentina, LATAM) works fine, both speakers (front and rear) and headphones.
When the headphone amp starts to clip/overdrive, this is accompanied by an unplugging event for the headphones. Artas' CM11 and CM12.1 are affected, too, but I could get my P760 to work with decent and stable sound output. While in Rammar's PA sound volume was even lower than with the stock rom(too low for even bothering to take the headphones with me) , CM12.1 is loudest. In order to not accidentially trip clipping and unplugging events, which will also reset volume to safety level, requiring to turn it up and clip again etc etc, Ilimited max volume to 80% in the Headset Button Controller app,which allows to control volume via headset mic button.
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Atronid said:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Click to expand...
Click to collapse
Thanks for your reply!
Yes, I do have used ROMs compatible with my device as they've all are made for espresso3g (which is my device).
I know it's not really the best way but I'll keep on trying with custom recovery for some more time and then perhaps try buying a new cable, and see if that works.
Tried installing Google Play Store from APK both on a clean ROM without GApps and with, but it still doesn't run and keeps on saying that either Google Play Store or "com.google.process.gapps" has stopped.
Alright...
I'm out of idea x/
lordquestionmark said:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
r&xp said:
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
Click to expand...
Click to collapse
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first seems to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
lordquestionmark said:
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
Click to expand...
Click to collapse
Ok...
This is what I would do if it was my device and I was facing what you are describing. It might take some time and a little patience to do everything described here, but it might also work.
1. Usin Odin, flash latest available official rom for the device. Let it boot and complete setup.
2. Use odin and use CF autoroot to root. Again boot and complete setup.
3. Flash Twrp. Enter Twrp and flash latest flashable supersu.zip. At this time I believe is version 2.82. Again boot and let it reach your welcome screen.
4. Enter Twrp. Enter advanced wipe. Wipe everything except external SD and usb at least 3 times. Do not exit twrp.
5. Install you rom. Do not exit Twrp.
6. After installing your rom, Twrp will ask you if you want to wipe cache/dalvik. "Yes" but DO NOT reboot.
7. Install correct version of gapps for your custom rom (correct both android version and architecture version). Again twrp will ask you to wipe cache/dalvik. "Yes" and this time reboot.
See what happens. If it gets stuck, try entering twrp again and do a factory reset only, only once and reboot again.
If that fails again... I will at a loss here myself too...
I did a quick search here on xda on P5100, I am providing some links that you can take a look at. You probably already searched yourself but you never know...
https://forum.xda-developers.com/ga...-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-blissmallow-t3312320
https://forum.xda-developers.com/showthread.php?t=1686514
https://forum.xda-developers.com/showthread.php?t=2581782
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candy-5-v2-5-5-t3136904
If nothing else helps, perhaps the best way to go around this would be to find a custom rom with at least some google apps pre-installed, in order to save you the trouble you are currently facing.
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
did you find a solution
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hey, just try uninstalling Google play services and install them again. I faced the same issue and now it's all working on my Samsung Galaxy Core 2
I'm very new to the rooting community, and I'm well aware of all of the problems. I've messed around, and bricked my phone many times but always knew how to fix it by flashing the custom rom. I've did whole of April until I figured out the proper rooting my model's for 6.0.1 software, and the 7.1.1 software. I eventually got tired of repeating this process, so in May (after I properly rooted my device and everything worked perfectly) I backed up everything including my system in TWRP.
Now the problem is, after using the xui tuner from xposed installer a bit, my phone seemed working for a bit, and lockscreen worked, but it randomly kept restarting at the boot animation . I grew impatient and restarted my phone properly a couple times but it kept rebooting after I unlocked my phone or just waited at my lockscreen. I then started got scared that I damaged something in my system or software, so I went to use TWRP to restore my backup (which I also literally backed up on this Tuesday). It apparently was successful, until the bootlogo freezing and saying my kernal wasn't SEANDROID ENFORCING.
Then now, I kept reformatting my data and restarting but it wouldn't work, it kept failing. So I gave up, and flashed my stock rom. This worked, but I obviously lost all my data. So to possibly help someone, I want to list what I think could've been the problem. (Still new, so I may list alot of unlikely things. Also random order)
1. I didn't format my data before the first restore, thus it failing.
2. Improper backup, I either backed up unnecessary partions like radio, or TWRP just didn't backup properly.
3. My sd card, I had many problems with my sd card before doing this type of stuff, but it went away during may. During may however, I backed up my magisk modules to it too, but they didn't appear on TWRP. Meaning it may have stopped working again. It also deleted my root folder, where I held the magisk zip and uninstaller.
Now this could bring another problem, I was using Magisk and Xposed installer, while also having my stock framework, xposed framework, and sony framwork (this was to use remote play), and in result my phone couldn't handle it and the module from both Magisk and Xposed.
4. I backed up my system while using the ashyx encryption zip, meaning when TWRP restored encrypted files?
5? XUI Tuner, I modified too many things with the app and probably did something to to the root directory. (Most likely Unlikely)
6. I modified my build prop by adding more code like the android users function, and TWRP probably couldn't back that up so it restored wrong like in 2
7? I modified TWRP by using a custom theme in the recovery, making certain functions like backup and restore not work?
8. I was using an old version of TWRP, 3.0.2 instead of 3.2 because 3.2. However, this is because 3.2 didn't work with my phone, and neither did 3.1.
I now flashed the stock rom, and everything works again. I just have to re-root. I didn't lose much data really, and I backed up some stuff in samsung cloud anyway. I just wanted to make this thread so I can fix the problem properly in the future, in which someone else may need it too. This model of samsung phone really isn't popular in the community, so it really would be helpful to other people. The solution could also work for other J700 variants, especially J700T1 since it's the most similar.
P.S. This is also just a small thing to help people too. Rooting this model is actually pretty easy, there's just a catch for one version of it.
6.0.1 can easily be rooted, especially with autoroot. It's works well, and you don't have to lose anydata at ALL! However magisk is untested.
7.1.1 on the other hand does require to format it's data to work so you have to back up anything you want to keep.. Superuser for me made wifi and the flashlight inaccessible, so I had to use Magisk. Which worked fine. There are two different versions of this root though. (Tested Once) One is basically like how the stock rom and has the manual, mobile data quick setting, and battery settings. to get it, don't use ashyx encrptyion . The other is like how you got it your device and set it up normally, no manual or extra settings, and requires ashyx encryption for this. The one I used was the ashyx encrpytion, and I was fine using this method because I kinda already lost everything over and over so I didn't care (end of april).
Edit: Turns out the stock version happens when you flash the stock rom, then immediately flash a custom recovery, and formatting the data without launching the the phone. I think this happens because when you get your phone, and activate it with a carrier sim card it downloads the additional files for that carrier which allows and when you format the data it formats the carrier version instead of the default system on the phone.
I hope we can find a solution for the kernal problem, so other people can fix this properly.
I would also like to ask if someone can make a odin and TWRP flashable kernal file of both the 6.0.1 and 7.1.1 versions of the SM-J700 variants, but for now in this thread the J700T is fine, unless all variants have the same stock kernal. This could be a solution and very helpful.
I have a USA T-Mobile Samsung Galaxy J7 J700TUVU3BQK3 phone and Can someone give me links to where I need to download the firmware ROM for this phone & all the different software I would need to root this phone or modify-backup its operating system??? My computer operating system is windows and also does anyone know how to setup a multiple operating systems on a computer where u can choose to either boot to different versions of windows and lynux.?? Computer Lenovo Gaming Laptop & HP Pavilion Laptop.
Hi,
last week I bought myself a Huawei P20 Lite as this one seems to be good comprise between size, speed and price and all together I find this device quite nice.
However I'm not a big fan of this ROMs, it's bloated and you have to confirm on each and everyhting, so I tried to reduce this dramatically and I began a long journey....
Unlock the bootloader
When I bought the device I wasn't aware about the issues that I may face (Downgrad, additional 4 Euro to spend) but OK, I thought it would be worth....
Installing Recovery
..but I couldn't be more wrong. It seems that there's no working TWRP for this device out there. I tried a lot, both on 8.0 and 9.1 but each time I tried to
wipe cache/dalvik the whole system got stucked and wasn't able to show the boot animation. So, assuming that there's really no working recovery out there, I continued to
directly flash different ROMs and try out my luck.
Rooting
This wasn't as hard as I though first, at least, as long as the ROM I've used had an advanced Reboot-Menu with the possibilty to boot to recovery, otherwise you end up somewhere in the desert and
may not be able to restart with boot.
The problem is, that this device required to patch the RECOVERY_RAMDISK partition, so in order to have Magisk booted, you required to use the Recovery. No big deal: just Power up
using VolUp and Power until the Huawei logo appears... normally.. It didnt work in more than 50% of the times...
Gapps (or Magisk)
OK, as I already indicated, I tried lots of them, but to be honest, none of them really convinced me (all was done on EMUI9.1 "AB" and not EMUI8 "A only")
GSI Phh Treble: nice, but this is one of thinks I did not checked in depth, as almost all (?) are based on this one...
OmniRom from OpenKirin: works perfectly out of the box, SafeteNet is working, Magisk can be installed, but no advanced boot menu and I find it a little bit overloaded...
MicroG ufOffical: I would go with it, everyhting worked, it's slim BUT I couldn't get my Banking-App working, not even after appliying multiple MagiskHide Prop-Settings...
Descendant: This one was by far my favorite... Really slim, advanced reboot-menu, but I couldn't flash Gapps. OK, so I tried MicroG: this can be installed using Magisk. After some trouble (e.g. you have to install DroidGuardHelper so that the OS recognizes an "Update") I got MicroG working, but I coulnd't get it with my Banking-App. In this ROM I couldn't even apply any MagiskProp Hide-Settings. Only Post-FS worked. OK, as I'Ve failed using this approach, I thought: maybe I can use Gapps with this image.... but as I stated at the beginning: I do not have any working Recovery.
So my questions:
Is there any working Recovery out there? TWRP 3.3.x supports to be flashed in RECOVERY_RAMDISK (and there's also offical support for P20 Pro) As of now I wouldn't even care about decrypted data, but at least be able to wipe and do a factory reset....
Or: Is it possible to install Gapps from a running (rooted) system?
Or: can I patch system.img with Gapps before flashing it to the phone?
But perfectly: did anyone get Descendant running with MagiskHideProp? Maybe even got MicroG running on it?
I'm currently out of ideas, did someone else had such a trouble with that device?
Best regards,
Peter
Well, yes. Kinda the same as you but I didn't try that many roms. I tried a fair bunch of twrp versions though. And I managed to use twrp to flash roms and if I remember well even do a dalvik/cache wipe with one of them - but I might be imagining that one. It is worth noting that you can actually use some twrp versions for other huawei devices on the p20 lite. Try at your own risk. There is a lot more development going on for the p8 lite (2017) for example. I tried the lineageos version that was posted herefor that device and it worked quite well.
I don't know what's wrong with this phone, but once it's rooted it will eventually enter a boot loop after some restarts or power on/off cycles. You can boot to recovery or fastboot, but no matter what you do there, the only way to fix the bootloop is flashing the stock boot and recovery partitions and formating data from there. The phone will reset to factory and boot up normally, but you will loose all your config, apps, etc. It's a pain in the a** to setup everything all over again every few days. Every time you have to restart your phone is like playing russian roulette, you never know when the boot loop will happen, but it will come up sooner or later no matter what you do. I have performed a lot of tests just rooting and without touching a single thing in config or apps, after some restart cycles it boot loops.
I'm fed up with it because it's so unreliable, it may work fine if you use it stock but I personally need root. I have ended up being so afraid of restarts that I have not powered it off or restarted since a month.
By the way this is my first One Plus and I don't know if this issue happens with other models from the brand.
This is just my experience and my advise.
Even i am a nord 2 owner and currently i am running custom os android 12 , even before this i had no probs like this with root.....
I bricked my device while installing gsi but that was different...
[RECOVERY][UNOFFICIAL] TWRP 3.6.0_11-0 for OnePlus Nord 2 5G [denniz]
Team Win Recovery Project 3.x, or TWRP 3.x for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven...
forum.xda-developers.com
Fastboot reboot recovery
Do this, then flash latest magisk....
You'll be good
satanishere16 said:
Even i am a nord 2 owner and currently i am running custom os android 12 , even before this i had no probs like this with root.....
I bricked my device while installing gsi but that was different...
[RECOVERY][UNOFFICIAL] TWRP 3.6.0_11-0 for OnePlus Nord 2 5G [denniz]
Team Win Recovery Project 3.x, or TWRP 3.x for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven...
forum.xda-developers.com
Fastboot reboot recovery
Do this, then flash latest magisk....
You'll be good
Click to expand...
Click to collapse
Indeed that's what I tried first because I usually solved boot loops with that method in other phones in the past. But with this one that trick does not work, I tried with several magisk versions before trying other things that didn't work either such as restoring a nandroid backup with TWRP or wiping everything and formatting data on TWRP. The only thing that worked was the method I described in OP, which I found in other thread in this forum. I have read reports about other people suffering the same problems, so I know I'm not alone.
By the way it seems to happen only with stock ROM. Which custom ROM are you using?
Regards
Pixel experience android 12....
Dev tab
Hi,
I can confirm that I had the same problem as you to root 3 One Plus Nord 2 (DN2103) from different friends wishing to stay on OxygenOS.
The root works fine and then totally randomly the OnePlus animation keeps looping after a reboot.
By doing a "fastboot -w" it starts again correctly but obviously with a loss of data.
Recently I got a Nord 2 from a friend for testing and it turns out that using the latest version of Magisk Canary, the root seems to remain after several reboots but to be tested over several months.
I've also seen here owners of European Nord 2 who confirm that root works well with Magisk Canary.
Edit : After about 10 reboots, the phone went back to bootloop.
Yes it's really exhausting root this phone. I tried custom roms without any problems with Magisk but stock is broken somehow. I need to use stock because of video recording quality. I have now Magisk 24.3 but didn't really restart it yet because of this. You shoud backup all data before restart . You can use data format in twrp, that works too.
Sperafico said:
Hi,
I can confirm that I had the same problem as you to root 3 One Plus Nord 2 (DN2103) from different friends wishing to stay on OxygenOS.
The root works fine and then totally randomly the OnePlus animation keeps looping after a reboot.
By doing a "fastboot -w" it starts again correctly but obviously with a loss of data.
Recently I got a Nord 2 from a friend for testing and it turns out that using the latest version of Magisk Canary, the root seems to remain after several reboots but to be tested over several months.
I've also seen here owners of European Nord 2 who confirm that root works well with Magisk Canary.
Click to expand...
Click to collapse
Thank you very much. Next time I will try switching to magisk canary channel. I'm on stable and sticking to 24.1 because the last time I updated from that version to 24.3 I got into a boot loop.
8vasa8 said:
Yes it's really exhausting root this phone. I tried custom roms without any problems with Magisk but stock is broken somehow. I need to use stock because of video recording quality. I have now Magisk 24.3 but didn't really restart it yet because of this. You shoud backup all data before restart . You can use data format in twrp, that works too.
Click to expand...
Click to collapse
Thanks for your answer. In my case the first thing I tried was flashing magisk again, then restoring a full nandroid backup with twrp, and then formatting data in twrp, but none of these steps worked.
I also heard about this problem being solved in custom ROMs but I haven't found any that fit my needs or any that has everything working, so I prefer to keep on rooted stock.
#metoo . We need devs to look into this problem. Been using rooted Android phone for years but now it s***s without root on Nord 2.
As long as you use an untouched stock rom (or after modding re-flashed by OnePlus servicepoint, rebooted into stock recovery, wipe all and re-flash stock, in a OnePlus store), root works fine on stock rom. Every attempt different than above will fail one day or another. I decided not to take OTAs because too many things can go wrong / turn unstable.
The phone is my daily driver, also for work. But I am rooted with Magism 24.3 (stable) and have various modules running including LSPosed, Shamiko, USNF, and in LSPosed GravityBox, XprivacyLua pro and a few more.
Works awesomely. Just don't touch things afterwords. In that case, yes, the phone sucks. Big time.
Xatanu said:
I don't know what's wrong with this phone, but once it's rooted it will eventually enter a boot loop after some restarts or power on/off cycles. You can boot to recovery or fastboot, but no matter what you do there, the only way to fix the bootloop is flashing the stock boot and recovery partitions and formating data from there. The phone will reset to factory and boot up normally, but you will loose all your config, apps, etc. It's a pain in the a** to setup everything all over again every few days. Every time you have to restart your phone is like playing russian roulette, you never know when the boot loop will happen, but it will come up sooner or later no matter what you do. I have performed a lot of tests just rooting and without touching a single thing in config or apps, after some restart cycles it boot loops.
I'm fed up with it because it's so unreliable, it may work fine if you use it stock but I personally need root. I have ended up being so afraid of restarts that I have not powered it off or restarted since a month.
By the way this is my first One Plus and I don't know if this issue happens with other models from the brand.
This is just my experience and my advise.
Click to expand...
Click to collapse
shoud what can i do any bramhastra or something ?
Look basically i am nerd and i agree that so apart from root i have question that installing TWRP and Custom Rom,is that working correctly with no issues? particularly pixelos
[email protected] said:
Look basically i am nerd and i agree that so apart from root i have question that installing TWRP and Custom Rom,is that working correctly with no issues? particularly pixelos
Click to expand...
Click to collapse
TWRP and custom roms works without issue. Even root is working with custom.
NANDroid does NOT work on stock rom! TWRP does, but no NANDroids possible.
Unfortunately I agree...
I spent so much time because of manipulations that I am used to doing, and which leads to a boot loop and a brick of the phone immediately afterwards.
The only solution I had was to flash the rom, which of course leads to a total reset each time and a considerable waste of time.
This is my 3rd and last OnePlus phone that I buy, I'm sick of all my lost data and hours spent just getting it started.
Oh my oneplus nord 2 is now in final bootloop. Cant make anything work, just keeps rebooting when plugging in power so $350 down the drain. Would not recommend..
Why down the drain? It's not 1 year old, so Oneplus will renew firmware under warrantee.
Xatanu said:
I don't know what's wrong with this phone, but once it's rooted it will eventually enter a boot loop after some restarts or power on/off cycles. You can boot to recovery or fastboot, but no matter what you do there, the only way to fix the bootloop is flashing the stock boot and recovery partitions and formating data from there. The phone will reset to factory and boot up normally, but you will loose all your config, apps, etc. It's a pain in the a** to setup everything all over again every few days. Every time you have to restart your phone is like playing russian roulette, you never know when the boot loop will happen, but it will come up sooner or later no matter what you do. I have performed a lot of tests just rooting and without touching a single thing in config or apps, after some restart cycles it boot loops.
I'm fed up with it because it's so unreliable, it may work fine if you use it stock but I personally need root. I have ended up being so afraid of restarts that I have not powered it off or restarted since a month.
By the way this is my first One Plus and I don't know if this issue happens with other models from the brand.
This is just my experience and my advise.
Click to expand...
Click to collapse
U r wrong
I'm not sure if it's just a coincidence, but for me, it always happens after about a week or two of ignoreing "you have an update available" popup. I thought maybe it modified the boot image, like magisk, to run at the next startup.
I agree that this is very annoying. If I didn't need Google Pay, I'd just install another rom.
Like said. Have your device Factory-flashed by OnePlus, REBOOT to stock recovery, do a FULL WIPE and FACTORY FLASH stock AGAIN! Only with the official OnePlus tool and software.
Only this way all your old fiddling around is erased. If you ROOT then, all will be fine. Of course, neglect further updates, but the device will work fine. Mine is in this state, heavily tweaked (Magisk, Zygisk, USNF, GravityBox, etc. etc. and it runs stable for over 10 weeks without any hickup.