yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Mini Questions & Answers] allanj:
My Axon 7 Mini developed an odd issue today. Normal use, then it rebooted and shows the Axon screen for ages, before then showing an error message stating that Telephone has stopped. Click okay and it says System UI stopped. Then back to telephone, and an endless loop until it reboots (presumably a watchdog somewhere). The same happens in safe mode.

No changes from the ZTE stock - this is running 6.0.1. I didn't enable USB debugging before, and I can't now as I can't get any kind of functional UI. Booting into recovery mode is possible, but without USB debugging enabled, I can't do much there. I've tried clearing the cache from the recovery mode, but that made no difference.

Does anyone have any suggestions as to what might have gone wrong? And / or, how I can pull the files off the device?

Thanks,

Allan
[ZTE Axon 7 Mini Questions & Answers] MrWhite0429:
Have you tried a factory reset?

Possibly use one of the stock firmware files found in the development section to upgrade to nougat?
[ZTE Axon 7 Mini Questions & Answers] allanj:
Yup - was hoping to avoid that, but I've just done that and it works after a reset.

Thanks for your reply!
[Samsung Galaxy S8+ Guides, News, & Discussion] aniel:
Hi,

I have a samsung s8+ i was playing with odin etc. Now is the different version of firmware on it. It is the SM-G955FD (dualsim) buut my phone is just one sim.

How can i change it to the just firmware.

A need please help.

thnx

Aniel
[Samsung Galaxy S8+ Guides, News, & Discussion] thatsupnow:
What different firmware version is on it?? Maybe give some more details
[Samsung Galaxy S8+ Guides, News, & Discussion] aniel:
Hi,

Now on the phone:

Model : SM-G955FD

Buildnumber: NRD90M.G955FXXU1AQ19

But it is a S8 Plus with only 1 sim

thnx
[Samsung Galaxy S8+ Guides, News, & Discussion] the_scotsman:
That makes no sense?

The SM-G955FD and SM-G955F use the same firmware.

The only way that would happen is if you flashed a SM-955FD specific firmware. it won't cause any problem or affect your device in any way.

But it would help to know exactly what you did while you "were playing" in Odin.

If you tell us which country or carrier you are with, we can find the correct firmware for your device and you can flash that back and it'll be back to how it should be, if you really want to get it back to normal.
[Samsung Galaxy J2 Questions & Answers] mozzafar alali:
Hello

I have J2 Prime (G532f) and I want to reset the pattern lock screen without losing the contacts and any of its data

I searched a lot on solution for this problem but I coudn't find any

is there any way to reset the pattern lock without losing at least the contact list ?
[Samsung Galaxy J2 Questions & Answers] Rauf_Baku:
Today a client broght me this model with screen locked. Firmware was G532FXXU1AQG2. I just flashed COMBINATION_OXE_FA60_G532FXXU1AQD1_OXE1AQD1_CL11108991_QB13167601_REV00_user_mid_noship_MULTI_CERT and now I can access all of data of this phone except CONTACTS. You must flash only boot, recovery, and system partitions. Do it easily with z3x box (uncheck all partitions except these three partitions). After back up all of data flash your phone again with official 4 file firmware.

SCREENSHOT

İf you want Contacts only way is EFT Dongle.
[Google Pixel XL Questions & Answers] sd_matto:
Trying to get Pixel XL 8.1 activated on Total Wireless (Verizon MVNO) to work with data (i.e., cellular APN).

Calling and texting work, so I am (almost) certain it is a cellular APN issue.

I go into Settings -> Networks -> Mobile Data -> Advanced -> Access Point Names (i.e., APN), and find nothing on screen, and nothing highlighted.

Stock APN does not work. And, I cannot find anywhere ability to edit or add cellular APN.

I have tried modding the apns-conf.xml file under /system/system/etc (followed by a factory reset to regenerate APN list) to no avail.

Downgrading to Android 8.0 until ability to edit/add cellular APN can be done. Would appreciate any help in getting cellular APN modded under Android 8.1
[Google Pixel XL Questions & Answers] sd_matto:
I got it to activate on Total Wireless (Verizon MVNO) on Android 8.1 by installing 8.0, activating on 8.0 (and confirming data working), and letting the beta 8.1 install via OTA.

Weird result that OTA works to activate, but that factory image does not.

EDIT: I since lost my cellular connection because my 8.1 phone could not show the necessary "TRACFONE.VZWENTP" APN; reverting to 8.0 fixed the cellular APN permanently
[Google Pixel XL Questions & Answers] crazykas:
It's right there..I can edit current apn and add new one as well..see attachments
[Google Pixel XL Questions & Answers] sd_matto:
On Android 8.1? That's a surprise.

Who is your carrier? And, do you have a carrier SIM, or an MVNO SIM (where you are piggybacking on a Big 4 carrier's towers)?

Using SIMs from my 2x Verizon-based MVNOs, the APNs are hidden. I did not capture screenshots (though I will on 8.1 final).

When I investigated by adb pull-ing the apns-conf.xml file at /system/system/etc to see what was going on, I noticed that there was a new menu item under each of the Verizon MVNO-based APNs, labeled "user_hidden" with "true" and "false" as options. All of the ones having to do with Verizon MVNOs had the label with option "true" (i.e., implying that the APN would be hidden from user, which is what I experienced).

Though I was able to maintain my cellular connection in doing the OTA from 8.0 to 8.1, I since lost it and was unable to get it back (neither network reset nor factory reset worked). So, I reverted to 8.0, and have the stable "TRACFONE.VZWENTP" APN going strong.

It would be a sad day if Google removed the capability of APN editing in 8.1 as another way to lock their phones.
[Google Pixel XL Questions & Answers] fiffan86:
I have TMO and I can edit and add apns. Might be something with Verizon and their MVNOs why they aren't showing up
[Google Pixel XL Questions & Answers] fiffan86:
Here are screenshots
[Google Pixel XL Questions & Answers] crazykas:
Im using mobitel (sri lanka) and yes im on 8.1. However i didn't update to 8.1 via OTA. I flashed factory images manually. I think this is only for Verizon..However you can ask them about this
[Google Pixel XL Questions & Answers] deskjet390:
How I accomplish this on my Pixel XL (and other phones that have locked apn settings)

This is what I have to do because my carriers apns are not in the Pixel XL's database and wrongly detect them as Verizon.

1. First off you need to have root.

2. After root, you need to hook phone into PC and access adb shell with root permissions.

3. After that.... issue this command

content query --uri content://telephony/carriers/preferapn

This will tell you which APN your phone is using at this current time. I have found it easiest to edit the APN your phone is using already. You then look where it says "_id=SOME NUMBER"

4. Once you know what number your phones APN settings is using then its time to issue the commands to edit that apn Number field

Replace SOME NUMBER with whatever apn number you are editing. Below is the syntax to edit the most usual apn fields. A good thing to do would be to obtain your APN settings and I may be able to help you find out what fields you need to edit

content update --uri content://telephony/carriers --where "_id=SOME NUMBER" --bind type:s:"default,dun,mms"
content update --uri content://telephony/carriers --where "_id=SOME NUMBER" --bind user:s:"phonenumber@whateverwireless.com"
content update --uri content://telephony/carriers --where "_id=SOME NUMBER" --bind mmsc:s:"http://mms.whateverwirelss.com"
content update --uri content://telephony/carriers --where "_id=SOME NUMBER" --bind mmsport:s:"whateverport"

This is what works for me 100 percent to get the right APNS in a verizon MVNO or Verizon LRA carrier partners apns programmed into whatever device i want to.
[Google Pixel XL Questions & Answers] Bryanx86:
This is what works for me 100 percent to get the right APNS in a verizon MVNO or Verizon LRA carrier partners apns programmed into whatever device i want to.[/QUOTE]

I was hopeful when reading this that I would be able to do this, but in adb shell I get all types of java errors. I'm updated to latest pureNexusADBTools. Are you getting errors trying this on Android 8.1?
[Google Pixel XL Questions & Answers] Bryanx86:
I have found an app that is missing from the 8.1 Dev preview and it is, of course, VZWAPN.apk. Placing this file where it would go on 8.0 doesn't work on 8.1.:(. Best, easy option is fastboot update zip, not fastboot -w update.zip. If anyone has a better or working way to change apn settings for Verizon specific carriers, please lmk.
[Google Pixel XL Questions & Answers] Bryanx86:
Vzw
[Google Pixel XL Questions & Answers] relaxable:
The java errors would be because you don't have root in the adb shell. IOW - after adb shell, your first command needs to be: su (and on the phone itself, grant su permission)
[Google Pixel XL Questions & Answers] Old Man Dave:
Thank you very much!!! I've been without data since yesterday because my APN wasn't right an I couldn't edit it as it was greyed out. Thanks to your post (and the multiple examples you threw up) I was able to fix my protocol and have my data back.

If anyone else has data connection issues and stumbles upon this, here's the command I used:

content update --uri content://telephony/carriers --where "_id=SOME NUMBER" --bind protocol:s:"IPV4V6"
[Google Pixel XL Questions & Answers] deskjet390:
This Works for 8.0 and 8.1 Devices

I came up with a new way that solves this issue.....no root required

I have confirmed this working on two Android 8.1 devices that use Verizon MVNO's (Pixel XL and Pixel 2 XL)

1. Turn phone off

2. Take out sim card

3. Boot phone up

4. Enable usb debugging and connect to PC

5. open up an ADB shell (if you dont know how to do this then do some research)

6. enter the command

am start -a android.intent.action.INSERT content://telephony/carriers --ei simId -1

7. This will open the "Add new APN" activity.

8. Fill in all the APN info you need to and name it whatever you want and then click save in the the menu options up top.

9. Once you save the APN...turn the phone off

10. Insert SIM again

12. Turn phone on and let it boot up.

11. Go to Access point names in settings and select the new APN you added.

Have a good day
[Google Pixel XL Questions & Answers] bestmvno.com:
Dialer Codes

Have you or anyone else tried using dialer codes? I got the right APN to show up for Red Pocket Verizon using a dialer code on a G4 Plus with an 8.1 ROM. The APN's can't be added otherwise. I'm looking for someone with Pixel devices to test out this solution with any Verizon MVNO such as Total Wireless.
[Google Pixel XL Questions & Answers] deskjet390:
What dialer code?
[Google Pixel XL Questions & Answers] bestmvno.com:
*#*#4636#*#* is the dialer code. This would be a multi step process though, not just typing in that dialer code. It would involve changing some settings you gain access to with that dialer code, and then resetting apn to default.
[Google Pixel XL Questions & Answers] deskjet390:
Would it involve turning "carrier provisioning" off and then resetting something back to default?
[Google Pixel XL Questions & Answers] kamikazeedriver:
closer than i was

This did work for me to get to my APN settings. Now just getting the right APN settings.

I tried the first setting listed here: https://bestmvno.com/apn-settings/total-wireless-apn-settings/

My phone wouldn't let me us 'dun' as an apn type, so I switched it to 'mms'.

I do have internet and it is nice and speedy, but I can't send picture messages.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Falkon.Nightsdale:
Greetings,

finally, I got new mainboard for my SG4 mini (meantime suffering from the curse of Meizu MX4 paddle) and I'm thinking about tweaking it a bit before putting it to full use.

So, since I have little to zero knowledge (except rooted Huawei Ideos X1), I would really appreciate any advice on how I can improve its function or which SW I should install on my desktop and pair it with my phone, etc.

There were some discussions back in 2016, but maybe something new emerged - after all, SG4 is one of the last one-handed-phone.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] IronRoo:
nothing much as changed. You need Odin and the Samsung drivers installed on your PC (widows). I'd then go for the official LineageOS ROM, white latest TWRP, if your model is supported by them both
[Magisk] NTchrist:
In the other thread, people were talking about using Kitchen to unpack, repack, and then push a boot.img... I'm not convinced it's doing what we think it's doing.

Let me explain

Unpack the boot image, delete everything in the ramdisk folder, create a dummy folder and dummy file so the repack tool doesn't choke, and then repackage the boot.img. Flash this to both boot_a and boot_b.

What would you expect would happen?

big ol' bowl of bootloops?

you'd be wrong; the system boots just fine as if you hadn't done anything.

This might explain why none of the options we set in prop.default are being respected, and why none of the system changes I attempted to make in init.rc were being applied. I have no idea what voodoo it's doing but it's not the behavior I would expect when I attempt to compile and flash a functionally garbage boot.img

Either that or I'm just a moron and don't understand what I'm doing... which is entirely within the realm of possibility.

edit: steps to replicate

1. extract boot.img from taimen-opd1.170816.010-factory-c796ddb4

2. ./unpackimg.bat boot.img

3. delete everything in the newly created .\ramdisk folder

4. create an empty folder, and an empty text file in .\ramdisk

5. ./repackimg.bat

*note that you now have a ~16mb boot.img*

7. .\adb.exe reboot bootloader;

8. .\fastboot.exe flash boot_a "PATH_TO_\image-new.img"

9. \fastboot.exe flash boot_b "PATH_TO_\image-new.img"

10. reboot

*note that system boots normally, get another beer

---------- Post added at 04:44 AM ---------- Previous post was at 04:31 AM ----------

now here's the really ****ed up part. I can flash a cf-auto failed boot.img and replicate bootloops, and then flash my (assumed garbage boot.img) and it then boots up again normally
[Magisk] DespairFactor:
On kernel side to remove verity from vendor, I removed the vbmeta struct code from both the LGE/HTC dtsi files and removed the avb flag from vendor, this will compile a dtbo.img without verity flags on it. Furthermore, I have tried to force initramfs not to be skipped at the source level, this causes it to boot into recovery only.

Next steps were hex patching the kernel image without verity at source level, this causes bootloops still as the hex patch applies something to the image causing the bootloops. I haven't done a full diff on what occurs when we completely repack the image, but if we swap the kernel image after a repack from magisk, it boots fine. The problem is only encountered with the hex patch. When the device boots without the hex patch, root is nowhere to be found, which leaves us wondering why the patch is needed if this code is all manipulated at the source level.

There could be potential issues or missing things that could deliver the payload, but currently we are able to bypass verity, it seems. If anyone has any information or suggestions how to deliver the payload at this state, it could help advance the status of getting root onto this device.
[Magisk] frap129:
I'm a bit confused by this and the post above yours. Are you saying that all of the initramfs files are used for recovery, and that the actual bootup process is somewhere else?
[Magisk] NTchrist:
This is what I suspect; it very clearly only breaks recovery when I modify the ramdisk in that manner.
[Magisk] slothdabski:
If it helps, here a new magisk just built from GitHub with latest commits

https://drive.google.com/file/d/0B1My3ELWb01vTnhsdXV1d1hyQUk/view?usp=drivesdk
[Magisk] NTchrist:
most annoyingly, I seem to have broken my stock recovery. It just boots to a "no command" screen, even after fully re-flashing the stock boot.img or the stock factory image. There doesn't appear to be a recovery zip in the factory image.(presumably, because it's entirely contained within boot.img now) [MENTION=5169465]DespairFactor[/MENTION] if you have any ideas there that would be really helpful. I want to try and play with my recovery's init.rc and see what kind of havoc I can cause but I can't do that without a stock recovery baseline and I have no idea how I could have broken it to the point where re-flashing boot.img doesn't fix it.
[Magisk] ScottIsMyName:
I don't think you broke recovery. Recovery is now within boot.img. When you get to the no command screen, you have to very carefully (you'll probably have try a bunch of times) hold power and then press volume up, and let go of both together. Eventually you'll get to recovery.
[Magisk] NTchrist:
that's different than "adb reboot recovery" or selecting "recovery mode" from the bootloader menu? Because that's how I get to "no command". The system boots just fine into either bootloader or android.

---------- Post added at 06:37 PM ---------- Previous post was at 06:20 PM ----------

For posterity, it's "hold the power button for 2 seconds, and then tap the volume up button" when you're at that screen. ok woo time to break ****!
[Magisk] frap129:
Update on this, just learned of a friend that initramfs files for system are now located in /vendor/init, and boot only contains the recovery ramdisk. So not only do we have to patch the boot img, but the vendor img as well.
[Magisk] slothdabski:
TWRP alpha builds are up for Pixel 2 and Pixel 2 XL

https://plus.google.com/+DeesTroy/posts/dUd6Mf2VPEv
[Magisk] ScottIsMyName:
If anyone has a build environment setup, [MENTION=4470081]topjohnwu[/MENTION] just made a commit that fixes another phone with a/b slots, so it may work for us too. If anyone can post a build, I can build a new image on the phone

edit: Was able to get the new binaries compiled and linked, but still bootloops :(

edit 2: The magiskinit binary is wayyyy bigger than normal, so perhaps something is not quite right with my build...it went from ~600kb to 4.5mb. So maybe someone else who has a proper build environment setup can try it still.
[Magisk] slothdabski:
FYI someone in [MENTION=5169465]DespairFactor[/MENTION] 's telegram group has the regular pixel 2. they claim they are able to root with magisk by building a kernel with selinux disabled and use the twrp alpha to sideload magisk 14.3 beta
[Magisk] ScottIsMyName:
I can confirm that setting the selinux policy to Permissive (with a custom kernel) seems to allow you to sideload the latest Magisk 14.3 zip in TWRP and it will root your device. However, this does not seem to work for the XL as we are still getting bootloops.
[Magisk] gururoop:
So, this can be done by flashing Snoke kernel on Pixel 2 and setting selinux to permissive using TWRP terminal and then flashing Magisk? Or is there any other method? I mean, do we need the kernel to permanently stay in permissive mode or we can put it in permissive by init.d script on every boot? Or we don't need to do anything else after rooting?
[Magisk] bryantjopplin:
Is your twrp decrypting like mine on the XL? I flashed the r7 root image from smoke and then booted into twrp and pulled boot image via adb shell dd if command and then flashed magisk and of course it bootloops but I pull the boot image via adb shell dd if command and unpack both. Magisk overlay folder and init were added correctly. I replaced the zimage in unpacked folder with the zimage from the original and it of course flashes. So it's just something it's doing to the zimage that's bootlooping it? Right?
[Magisk] slothdabski:
[MENTION=4470081]topjohnwu[/MENTION] can you shed some light on this? Any idea why xl loops when the p2 boots fine with permissive kernel and Magisk beta
[Magisk] DespairFactor:
Do you know of a way we can force it to never skip at source level? when I did it, it just boots recovery.
[Magisk] romracer:
It should be pretty easy to do. The code for this is in init/initramfs.c around line 624-625. Just comment out the if-block; this will force the kernel to use the initramfs included in the boot.img (ie. not skipping it).

I don't understand the second part of your question. As [MENTION=4470081]topjohnwu[/MENTION] stated, the boot.img initramfs only contains recovery files. By not skipping it, you are booting into recovery - so it sounds like you got what you wanted already? To re-quote:

It sounds like you've made it to step 1 (getting the device always booting recovery AKA ignoring the "skip_initramfs" kernel command line option).

The next step would be to repack the initramfs included in boot.img to replace the init binary with magiskinit. Then you would need to begin stepping through magiskinit's code as it works steps 1-7 [MENTION=4470081]topjohnwu[/MENTION] outlined, looking for differences or failures between Pixel 1 and Pixel 2.

It may not contain anything useful, but one other area I would point out for investigation is the init/noinitramfs.c source file. This code is executed to setup a bare-bones root partition (the "/" partition) when you ARE skipping the built-in initramfs (remember: we are not skipping the built-in initramfs, so this code isn't executed if Magisk is done properly). Perhaps it contains clues to improperly or missing setup of the root partition (compare this source with OG Pixel's same source).

Based on everything I've read in these threads (this one and the one in the P2XL forums), you guys think SELinux or the hex patching is failing. Well it sounds like hex-patching is working fine. Theoretically, it should be possible to comment out the SELinux policy patching (and maybe init.rc patching) in magiskinit and replace the original init with it. You'd have a magiskinit that sets up the root partition and not much else. It wouldn't provide root, but it might let you know if magiskinit contains enough code to even get the Pixel 2 XL to boot.

Unfortunately, right now, I do not have the time to spend getting Magisk running on my Pixel 2 XL. Hopefully this helps someone else get the ball rolling though.
[Magisk] xstokerx:
Version 14.4 from github installed fine from adb sideload in twrp alpha
[Magisk] slothdabski:
For which device? Root has already been achieved for pixel 2, pixel 2 xl is the issue
[Magisk] xstokerx:
Pixel 2
[Magisk] Itachisasuke:
Hopefully the below will make porting to the Pixel 2 XL a bit easier.