PLEASE HELP with new version qin F21, different hardware and ROM

You don’t need anything else, but you don’t have the modded nvdata :slight_smile:

Dunno if that’s where the imei is stored but if yes, that’s the reason I took it off.

Give me an email or some way to send you a link.

[email protected]

[email protected]

Okay I have a phone ready and waiting didn’t get any file?

1 Like

Will send

Sent. If it doesn’t work I have one more

File opens as a graphics file PNG tomorrow’s another day

1 Like

One step closer…

Also, my nvdata has more bands… just had it search one area

Strangest thing is that md1img has support for all US carriers, but they chose to neuter it.

Now the issue is actually making an edit that the device will boot with…

F30 md1img MDDB vs F21 v3 md1img MDDB

Made a patch that nullifies PLMN hash entries in md1img, with the hope that it falls back to nvdata for band selection.

Can’t use the f30s MDDB because of the different RF frontend hardware.

Will upload soon.

Sending to @Lamden613 and @dfrydman first

Again, all Claude, I have absolutely 0 experience with this stuff. Can only make educated guesses. But with the right analysis and direction… I’ve done cool things, and I learn along the way.

Why nullify instead of doing it properly? Simple, there ain’t no way I’m getting into Ghidra.

This needs to be flashed in combination with my modified nvdata.

3 Likes

Flashed the NV data file give me the IMEI but still no service on stock ROM did a search manually did not find any networks. I tried with both T-Mobile and Verizon Sims

I also sent you md1img. In the drive link I sent by email.

Flash both and do a factory reset

Let me see if the factory reset helps

Again, you need BOTH md1img and nvdata.

Nope still no good

Hello… lol

At the same time I did it before I’ll try again

And it goes in slot a correct? And I don’t have to rename the md1?

As long as it goes to the right position in memory

Use fastboot, no slots.