yashsingh1/xdaforums huggingface dataset:
[Nokia 1 Questions & Answers] shaz-hash:
Hello,

So I have been stuck in a bootloop when flashing my Nokia 1 (MT-6735) with a custom ROM. Basically, I followed the following guide from 2017 in this process.

In the linux kernel code released by the offical Nokia (here), I added few lines in few C files. SInce, Nokia 1 is ARM machine I used google's toolchain from 2019 to cross compile (here).

To execute the cross compilation process, there were some minor errors with the make files , largely due to the old dependencies, that I changed.

After the process of cross compilation, I got Image, zImage , zImage-dtb , & mtk.dtb.

Based on the guide, I used Android Image Kitchen to create .img file. However in this process, after unpacking, I replaced my file "boot.img-kernel" with the zImage and renamed the file to "boot.img-kernel". The problem is that now after flashing with fastboot using the cmd :

My device ended up in bootloop. My question is that is there any new guide that I can follow to allow me have my changed kernel code (slightly) to be flashed into NOKIA 1 safely.

I will be grateful for all the help.

Thanks 🙌
[Nokia 1 Questions & Answers] krynyx:
Probably the official kernel is signed and have verification on boot every time it is read from disk to the RAM. Flashing a different kernel maybe result on bootloop.
[Nokia 1 Questions & Answers] shaz-hash:
I doubt because the same mobile has been flashed with custom ROM that I got online for the root access.
[Nokia 1 Questions & Answers] krynyx:
My device is running a custom ROM, and supports root too, but with the stock kernel. If I try to install another kernel or install a different boot.img from another ROM version, or install a boot.img with different size of the current, it will results on hard brick.

Before flashing any package, you need to disable dm verity, or it will results on bootloop (hard brick).

See the following article to understand it.

https://source.android.com/docs/security/features/verifiedboot
[Nokia 1 Questions & Answers] itzParsaYC:
can you share the new codes?

this cause of a bad code, your new codes cannot run correctly and this creates bootloop on your device
[Nokia 1 Questions & Answers] shaz-hash:
Yeah I get your point now, it could be the result of this step ommitted. Thanks ! and i will get back to you soon with the outcome.
[Nokia 1 Questions & Answers] shaz-hash:
I don't think this would be the factor as for the initial step I just added "Printk" statements to see if the custom ROM works.
[Nokia 1 Questions & Answers] shaz-hash:
By the way, if possible do you have any guide with regards to how to disable this verity check.
[Nokia 1 Questions & Answers] krynyx:
It's made by fastboot commands like that:

fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img

You need to re-flash the vbmeta.img with this options. It will allow you to change the device content and partitions.
[Nokia 1 Questions & Answers] shaz-hash:
thanks, on it
[Nokia 1 Questions & Answers] shaz-hash:
Also, do you know of any guide that can allow me to get out of this bootloop (bricked phone) ?
[Nokia 1 Questions & Answers] krynyx:
It's a MediaTek MT6735, so disconnecting the battery is the first step to unbrick it.

Download the MTK drivers, disconnect the battery and connect the USB on computer. Check the "device manager" on windows to see how your device appears there. Getting your device recognized by windows is the first step to unbrick it.
[Nokia 1 Questions & Answers] shaz-hash:
Damn, thats cool ngl.

I would make a sketch of your avatar if you create complete guide on how to compile and flash nokia 1 with modified kernel code.💀💀💀 (just joking , appreciate all the help)
[Nokia 1 Questions & Answers] shaz-hash:
Successfully unbricked !

thanks @krynyx !!!!
[Nokia 1 Questions & Answers] shaz-hash:
@krynyx the problem is that i removed the verity check via Magisk. However even with the kernel code changed and using Stock ROM where i replaced my custom kernel zImage with its, the Nokia 1 is still on Bootloop. Any help that i can get. I can assure you that code changed is all correct.
[Motorola Moto G32] Harsh2434:
Can anyone suggest me best gcamport version for moto g32 which gives best results?
[Motorola Moto G32] Dayuser:
Check this thread.

Gcam for motog32

Help me find gcam for moto g32

xdaforums.com
[Motorola Moto G32] Badger50:
Thread closed as the topic already exists as stated above.
[Touch Diamond, MDA Compact IV Themes and Apps] wedgemoose:
Help Please. You guys are way too advanced for me. I am a desktoper at best but NEED this tool to do certain things wanted. When I start the program, it says "NULLReferenceException". I went to the "fix it link" but don't know how to do it.(not good in registry). You say to "delete the tweak.xml in program directory of my tool". HOW DO YOU DO THAT??? I tried the "change pressure threshold" in the registry but don't think I did it correctly. If anybody could give me details for a beginer, i would be in debt to you forever. I need to know how to changge a registry value or string or whatever I'm supposed to be changing. Also, maybe this shouldn't work on a brand new ;Verizon touch pro 2?? Am i trying for nothing?? If so what can I use instead. I want the "Dirty Paper" theme. Plus ten of the TF3D's other features. Please help.......Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] FuzzFuzz:
Have you tried total commander already?

With this program, it's very easy to change registry settings and it has a built in search function that works like a toad on a soap hill.

please, go here : http://www.ghisler.com/pocketpc.htm
[Touch Diamond, MDA Compact IV Themes and Apps] wedgemoose:
thanks fuzzfuzz. I will try it....
[Samsung Galaxy A22 5G] Aztechx1:
Is there any port or a way that I can install one UI 6 on my phone? (A22 5G)

Have already rooted my phone if that does anything.
[Samsung Galaxy A22 5G] Wazzin_1303:
quelqu'un répond s'il te plait 😪
[Android Head-Units] Grubenloewe:
Hey guys,

I'm owning a Junsun V1.pro and use the preinstalled autolink.apk for establishing a AA-connection. I wanted to ask if there are other apps here that I can use to stream AA on my head unit because I have a feeling autolink doesnt always use the right settings.
[Android Head-Units] -fluffy-:
I use carletter on my v1 pro
[Android Head-Units] Grubenloewe:
Thanks, I also read about ZLink. Where do I have the possibilty to get the apk?

Update: I just discovered that I can change to carletter in the settings menu but still need to activate it. Where do I get the code for it?
[Android Head-Units] -fluffy-:
From ur seller
[Android Head-Units] -fluffy-:
An for zlink theres a official z-link thread here in Android head unit
[Android Head-Units] -fluffy-:
[APP] Z-LINK Channels

Recently, I had a problem with the z-link app, when trying to update I ended up installing a version with the wrong channel, with that I ended up losing access to android auto and carplay. Searching the internet I couldn't find the channel I...

xdaforums.com
[Android Head-Units] PrinceLc:
Zlink won't work with the Junsun ! Ask seller to activate CarLetter it's nearly same like Zlink in speed
[Google Pixel 8] rw_on_xda:
does anyone have experiences with an in USA bought Pixel 8 / 8 Pro and the use in Germany (or Europe) ?

I've checked the Network/Radio Spec's and found some minor differences (LTE, 5G)from here:

Pixel phone hardware tech specs - Pixel phone Help

Take a look at the tech specs for Pixel phones. If you're interested in buying a Pixel phone, visit the Google Store. P

support.google.com

compared were:

Model G9BQD: For NA (US and CA) only [5G Sub 6GHz NA]

Model GKWS6: For NA (US and CA) only [5G mmWave + sub-6 GHz]

Model GPJ41: Rest of the world [5G sub-6 GHz]

for each Model Radio Spec's (for LTE and 5G) written among themselves for better comparation :

LTE Bands:

B1 2 3 4 5 7 8 12 13 14 17 18 19 20 25 26 28 29 30 38 40 41 46 48 66 71

B1 2 3 4 5 7 8 12 13 14 17 18 19 20 25 26 28 29 30 38 40 41 46 48 66 71

B1 2 3 4 5 7 8 12 13 14 17 18 19 20 25 26 28 30 32 38 40 41 42 46 48 66 71

=> the US-Models do not have 32, 42

and

5G Sub-6 Bands :

n1 2 3 5 7 8 12 20 25 26 28 29 30 38 40 41 48 66 70 71 77 78
n1 2 3 5 7 8 12 20 25 26 28 29 30 38 40 41 48 66 70 71 77 78
n1 2 3 5 7 8 12 20 25 26 28 30 38 40 41 66 71 75 76 77 78

=> the US-Models do not have 75, 76

so my questions is (with view/compartion esp. on US-Models and GPJ41):

Will the differences hurt somehow ?

P.S.

I've read there are more Models then the 3 above ...

any pointer to their spec's ?
[Google Pixel 8] Erecik:
I don't know how this may help You, but just to add some data.

I am using GC3VE in Poland which was bought on Amazon. Sadly I don't know what country uses GC3VE, but my P8P is working completely fine, 5G and LTE is working great.

1, 2, 3, 4, 5, 7, 8, 12, 13, 14, 17, 18, 19, 20, 25, 26, 28, 30, 32, 38, 40, 41, 42, 46, 48, 66, 71 - GC3VE

[5G Sub 6GHz]21 Model GC3VE

GSM/EDGE: Quad-band (850, 900, 1800, 1900 MHz)

UMTS/HSPA+/HSDPA: Bands 1, 2, 4, 5, 6, 8, 19

LTE: Bands B1 / 2 / 3 / 4 / 5 / 7 / 8 / 12 / 13 / 14 / 17 / 18 / 19 / 20 / 25 / 26 / 28 /30 / 32 / 38 / 40 / 41 / 42 / 46 / 48 / 66 / 71

5G Sub-621: Bands n1 / 2 / 3 / 5 / 7 / 8 / 12 / 20 / 25 / 28 / 30 / 38 / 40 / 41 / 66 / 71 / 75 / 76 / 77 / 78

eSIM

[5G mmWave + Sub 6GHz]21 Model G1MNW

GSM/EDGE: Quad-band (850, 900, 1800, 1900 MHz)

UMTS/HSPA+/HSDPA: Bands 1, 2, 4, 5, 6, 8, 19

LTE: Bands B1 / 2 / 3 / 4 / 5 / 7 / 8 / 12 / 13 / 14 / 17 / 18 / 19 / 20 / 25 / 26 / 28 / 29 / 30 / 38 / 39 / 40 / 41 / 46 / 48 / 66 / 71

5G Sub-621: Bands n1 / 2 / 3 / 5 / 7 / 8 / 12 / 20 / 25 / 26 / 28 / 29 / 30 / 38 / 40 / 41 / 48 / 66 / 70 / 71 / 77 / 78

5G mmWave21: Bands n257 / 258 / 260 / 261

eSIM

[For Japan only]

[5G mmWave + Sub 6GHz JP21] Model GE9DP

GSM/EDGE: Quad-band (850, 900, 1800, 1900 MHz)

UMTS/HSPA+/HSDPA: Bands 1, 2, 4, 5, 6, 8, 19

LTE: Bands B1 / 2 / 3 / 4 / 5 / 7 / 8 / 12 / 13 / 14 / 17 / 18 / 19 / 20 / 21 / 25 / 26 / 28 / 30 / 38 / 39 / 40 / 41 / 42 / 48 / 66 / 71

5G Sub-621: Bands n1 / 2 / 3 / 5 / 7 / 8 / 12 / 20 / 25 / 28 / 30 / 38 / 40 / 41 / 66 / 71 / 77 / 78 / 79

5G mmWave21: Bands n257

eSIM

FeliCa

View attachment 6058587
[Google Pixel 8] rw_on_xda:
surely it helps !

Thanks

it seems the GC3VE (Pixel 8 Pro) has similar LTE/5G Spec's as the GPJ41 (Pixel 8 [ without "Pro"])

GPJ41 (a non Pro Model) is for "Rest of the world", e.g. EU.

And it seems there is no "Rest-of-the-world"-Pixel 8 Pro.

means: Pro are usable worldwide, excluding the Japan ones

A last question:

What Firmware, esp. Modem-Country-Version are you running ?

US or sorta EU (EMEA) ?

see:

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com
[Sony Xperia Z Ultra] tarkzim:
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/

Introduction

LineageOS is a free, community built, aftermarket firmware distribution of Android 14 (U), which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

Bugs

What's working:

Boot

Bluetooth

Camera / Camcorder (Built-in camera is buggy, use OpenCamera instead.)

RIL (DATA/Call/SMS)

WiFi

WiFi Hotspot

USB (ADB/MTP/PTP)

NFC (not-tested)

LED lights

Sensors

FM Radio

GPS

Audio Playback

Video Playback

Touch screen

ExFAT SDCard

What's not working:

Hardware encryption

SELinux is permissive

You tell me.

Installation instructions

Download the zip(s).

Install a compatible Recovery

Perform a NANDroid backup of your current ROM (Optional)

Wipe system / data / cache partitions

Flash ROM.

Optional: Install the Google Apps addon package.

Optional: Install Magisk for Root.

Supported models:

C6802,C6806,C6833,C6843

Downloads

Recovery : My Unofficial TWRP

Gapps : MindTheGApps ARM 14

Rom : Download

Sources

Device/Kernel/Vendor Tree: Sources

Donate

DONATE To Me

Big Thanks

LineageOS Team.

AICP Team.

all sony-msm8974 / sony-rhine contributors.
[Sony Xperia Z Ultra] tarkzim:
Changelogs

2024/01/28

Fixed Bluetooth and BLE Audio.

2024/01/21

Initial release of LineageOS 21.0 for Z Ultra.
[Sony Xperia Z Ultra] dasrum:
I really want to test this on my C6833. Could you let me know how to install it? What kind of twrp should be used? do I need to install under android 5.1.1? or I need to install prior version of android first. If I have to install upper Android 5.1.1, whichi android version should I install on C6833.
[Sony Xperia Z Ultra] tarkzim:
New build released

Fixed Bluetooth and BLE Audio.
[Sony Xperia Z Ultra] dasrum:
I installed LOS21. just short test of the system. it is not stable and slow. I think LOS20 is very stable. but, I would like to test by latest one that may be fixed bluetooth.

I always want to say thank you.
[Sony Xperia Z Ultra] Contrary_op:
Hello @tarkzim, thank your for your continuous support. Its great to have someone like you with us.

You are great!

I'd like to talk a bit about my experience with the LOS21 release. I have the C6833 and I never installed any custom roms before so I am pretty new to this.

Anyway I managed to install your recovery and your LOS21. I wiped some cache (though I dont know if it maybe has something to do with my problems, (so if anyone would explain which things are important to wipe in the custom recovery):D Edit, i installed gapps too!

Anyway as @dasrum stated before, there is some strange performance issue with the system UI (seems to be the main problem). For some reason this makes the system unstable and sometimes unresposive for 15 - 20 seconds, sometimes with the system ui not responding warning popping up. Actual performance is good so its a bit strang. Did anyone have similar problems with los20?

Maybe we can find out if you people have similar experiences?
[Sony Xperia Z Ultra] tarkzim:
Yes, GAPPS was a known issue to cause system crashes, but they got fixed in sources, will be included in the next build if there is.
[Sony Xperia Z Ultra] cnd2:
I'm interested if you're planning on a new build! If there's doc for how to do the build myself, I'm also capable of doing that if you can point me at the resources.

I need my C6833's big screen for an accessibility project...
[Sony Xperia Z Ultra] 27iu:
Hello, first of all thanks for this ROM, never done anything like this before but I think I got it right. I managed to install it, but now my SIM is "Not availavbe" and IMEI and IMEI sv is "unknown"

Is there any way to fix this? Or should I try a different version of the OS?

I have the C6833 and used twrp-3.7.0_9-0.

View attachment 6092253

I also searched other threads and tried using this just in case, but it didn't work

Upd. Installed 20.0, everything works there​
[Sony Xperia Z Ultra] ulitko:
Same. Went back to 20.0 and everything worked.
[Sony Xperia Z Ultra] Spray_05:
Can I have the boot img of stock 5.1 rom z ultra I accidentally flashed the recovery img as boot and ****ed jt
[Sony Xperia Z Ultra] Spray_05:
Bro my device wont boot recovery can u help me
[Sony Xperia Z Ultra] omidsa596:
I have same problem.

Not detecting sim card
[Redmi Note 11 (spes/spesn)] KULDUS:
This application is available for some of your devices

hi why i cant download some app on my phone from store like adidas confirmed or coinbase pls help me
[Samsung Galaxy A52 4G] Visse0704:
Hello, I received the following smartphone (with the accompanying firmware version) new.

Galaxy A52 (SM-A525F)

Country: Germany

Model: SM-A525F

Product Code: MBC

Security Patch: 2023-12-01

OS Version: Android 13

PDA: A525FXXS6DWK2

CSC: A525FOXM6DWH2

Build Date: 2023-11-29

I would like to root the device and install custom ROMs and recoveries. Before proceeding, I wanted to inquire about the current status regarding my smartphone and firmware.

Can I root it normally using MagiskManager and flash custom recoveries with Odin, or is there a specific procedure?

Otherwise, should I simply follow the latest guides?

(For my old Galaxy S8, due to the latest firmware, I believe one had to root/flash with fixes and other patches.)

How can I best create a complete backup of my A52 before rooting/flashing? (ROM, IMEI, etc....)

Is it still possible with current devices to completely undo the rooting process and flashing without being detectable, or is that not possible nowadays?

Thank you for the information and assistance.
[Samsung Galaxy A52 4G] parrots_:
You should be able to root it with Magisk. I suggest you get the firmware and patch manually, just to make sure you avoid any issues with older binaries or firmware issues.

You can undo the root process, but it even if you undo root, it'd trip Knox and can't be fixed, so it'd show you modified it. Not only that, banking apps can detect root. There's some patches though.
[Samsung Galaxy A52 4G] Visse0704:
okay.

That way with the patched boot-img and VBMeta,right ??

Yes i would patch that manually.

This also works with the latest official firmware, or should I downgrade first?

When the phone is rooted, then just flash TWRP with the official TWRP app ?

Or for the first time with odin ??

and there don't seem to be any known complications when flashing a custom recovery, I assume?

Or suppose I just give it a try.

How high is the risk when flashing custom recovery that you could end up with a hardbrick?

That's my biggest concern, that somewhere in the guides on page 50++ it says that you definitely need this and that file or you'll get a hardbrick when you try to flash.
[Samsung Galaxy A52 4G] parrots_:
You don't always need a vbmeta, but you should probably do it to be safe.

The firmware should work on any version, you don't need to downgrade.

Once it's rooted, you can just install TWRP via Odin, Flashify, your choice.

Installing a custom recovery rarely goes wrong, so you should have no issues. Make sure you're flashing for the right variant.

Are you talking about the Magisk guide, regarding the hardbrick?

I found some posts about hardbricks with TWRP, it's usually because a wrong model, but fixable.
[Samsung Galaxy A52 4G] Visse0704:
So.

In the upcoming days, I finally have some time to get to work.

I've noticed there's also this "OrangeFox" Recovery. It seems at first glance to be even better than TWRP Recovery, right? (For example, due to Android 14 support.) I think I would go with that directly.

Doesn't the device actually get rooted automatically when flashing a recovery? Can't you save yourself a step through ODIN by simply flashing the recovery and then installing Magisk through the Manager app afterwards?

Otherwise, I just came across the following guide: https://www.androidinfotech.com/43541-root-samsung-galaxy-a52-4g-lte-android-13-sm-a525f-m/

It also explains directly how to patch your own Boot.img/VBMeta stuff. Can this guide be trusted?
[Samsung Galaxy A52 4G] parrots_:
Custom recoveries don't automatically root the phone. You can just flash the Magisk ZIP in recovery though, it should do about everything for you.

Also, the guide seems to be outdated, since it says Android 13.
[Samsung Galaxy A52 4G] Visse0704:
Outdated ?

Android 13 is the last official firmware for the A52 i thought ??

Alright, so regardless, do you have to go through all the steps regarding the patched boot.img/VBMeta only once per smartphone? Depending on what you do first (Rooting or Recovery), do you only have to go through the process once and after that, everything is basically manageable with regular flashing using zips/ODIN?

Sorry for the beginner questions. I just want to try to understand the basics (even if not down to the smallest detail).
[Samsung Galaxy A52 4G] parrots_:
I looked on SamFW, and there's a Russian CSC firmware for Android 14, for the same device.

From my experience, the VBMeta isn't needed, but if you wanna be really careful, you can select it. You only have to flash recovery or root one time, then it should stay. Doesn't really matter the order.

Only thing is that you have to boot into recovery after flashing a custom one, because booting into the system first immediately overwrites it with stock.

After that, everything should be manageable with ZIPs.

I think the Magisk ZIP checks for vbmeta if you flash a custom recovery first.
[Samsung Galaxy A52 4G] Visse0704:
Hey,

Here I am again. Freshly rooted :D.

So, rooting with Magisk on the latest official firmware finally worked for me after a few failed attempts and a better guide.

I ultimately followed this guide (https://topjohnwu.github.io/Magisk/install.html#samsung-devices).

The biggest difference from the guide I posted here before is probably that in the "official" Magisk installation guide, you let the Magisk app patch the entire AP file from the firmware. The other guide only mentions Boot.img and VBMeta. Then, I loaded all files (Patched_AP + BL + CP + CSC) into Odin, left Auto-Reboot enabled, and when Odin was done, I landed in Recovery, performed a Factory Reset, and after the ROM installation, Magisk installed/Roote itself automatically via the Magisk app.

Now, I'd like to put a custom recovery (TWRP or OrangeFox) on the device. Since I'm rooted and root persists after rebooting, I shouldn't need to patch anything anymore to get another recovery installed, right? Due to the root permissions, would it perhaps even be more sensible to install TWRP via the app instead of using Odin? (My layman's understanding would now assume that in the Odin process, more things could go wrong, and in the worst case scenario, if the flashing doesn't work, I might even lose root permissions, whereas if I just let an app with root permissions do the task, I wouldn't.)
[Samsung Galaxy A52 4G] parrots_:
Great, no issues?

As for the custom recovery, you don't need to patch anything else for it. It doesn't really matter how you install it. If I remember correctly, the TAR version of TWRP is just made up of a recovery image, so it shouldn't affect anything if it fails. If you wanna be safe, go ahead and just use Flashify or the TWRP app.