I am getting 5g for cdma-less on android 12, but not android 11, however, I like using android 11 better. So, is there a way to update the modem without upgrading the OS? Thanks
KHALISTAN said:
I am getting 5g for cdma-less on android 12, but not android 11, however, I like using android 11 better. So, is there a way to update the modem without upgrading the OS? Thanks
Click to expand...
Click to collapse
If there are no bootloader restrictions that can prevent it from flashing, you might be able to extract the modem img from the android 12 firmware and flash the modem by itself.
this the right command? fastboot flash modem modem.img
You don't think there'd be a conflict by flashing an android 12 modem with android 10 os?
KHALISTAN said:
You don't think there'd be a conflict by flashing an android 12 modem with android 10 os?
Click to expand...
Click to collapse
I don't know. It depends on the device and the bootloader. As I said in my post above...if there are no bootloader/binary restrictions.....
It's the Linux kernel that connects the user to the device's hardware components. Thus even with the default kernel driver, using another modem.img the modem may not work:
jwoegerbauer said:
It's the Linux kernel that connects the user to the device's hardware components. Thus even with the default kernel driver, using another modem.img the modem may not work:
Click to expand...
Click to collapse
It's the op8. Gets a signal on android 12, but no signal on android 10 after msm. That's why I'd like to upgrade the modem but nothing else.
Related
Hi,
After I manually erased all the partitions on my Pixel (Sailfish) by using fastboot erase < name of the partition) on bootloader screen (please don't ask me why I did that :-| ) , I am not able to install Android 8.1 or any newer Android versios on that. I can install only Andorid 7.11 to 8.0 versions from google factory image site.
if I install 8. 1 or newer version, the device constantly reboots and sometimes stops in stock recovery or on the bootloader screen. I have tried pretty much everything with no sucess. Before erasing partitions, phone was working fine with Android 10 with December 2019 updates.
I will be ok and satisified if I can at least get Android 8.1 with July 2018 updates. Can someone please help me figure out what the heck is wrong with my device. There is no physical, or electrical damage on the device whatsoever.
Thanks.
JanuGerman said:
Hi,
After I manually erased all the partitions on my Pixel (Sailfish) by using fastboot erase < name of the partition) on bootloader screen (please don't ask me why I did that :-| ) , I am not able to install Android 8.1 or any newer Android versios on that. I can install only Andorid 7.11 to 8.0 versions from google factory image site.
if I install 8. 1 or newer version, the device constantly reboots and sometimes stops in stock recovery or on the bootloader screen. I have tried pretty much everything with no sucess. Before erasing partitions, phone was working fine with Android 10 with December 2019 updates.
I will be ok and satisified if I can at least get Android 8.1 with July 2018 updates. Can someone please help me figure out what the heck is wrong with my device. There is no physical, or electrical damage on the device whatsoever.
Thanks.
Click to expand...
Click to collapse
There is a difference and something strange, that I can't seem to grasp, between any version of Android 8.0 or prior and Android 8.1 or newer. some partition(s), checksum or a flag seems to be off...goddamnit!:crying:
JanuGerman said:
There is a difference and something strange, that I can't seem to grasp, between any version of Android 8.0 or prior and Android 8.1 or newer. some partition(s), checksum or a flag seems to be off...goddamnit!:crying:
Click to expand...
Click to collapse
Well, I was able to get a copy of persist.img from someone online and restore the /persist partition on my OG Pixel (Sailfish) and now I am able to boot into Android 10. if someone needs any help in this regard, I will be more than happy to help. Thanks. ciao
Hello. I am fairly technical with web and computers but not so much when it comes to android or mobile hardware/sofware so bare with me.
I got my oneplus 7 pro 5g (UK EE network) back from repair yesterday and went to install lineage os on it following this tutorial https://wiki.lineageos.org/devices/guacamole/install with OpenGApps nano.
The install seemed to go fine and managed to boot into lineage, connected to wifi and then started installing my apps etc. Today I moved my sim over and could not get the phone to recognise the sim. Could not turn on mobile data, could not see a phone number in the about settings page etc.
I then started googling around and found this thread [OP7P] [Latest: 11.0.3.1] Android 11 Firmware collection | XDA Forums and in my limited wisdom decided to just start flashing the global firmware onto the device. After this lineage booted fine but now not only no sim/mobile network but also no wifi. I assume i have put the wrong firmware onto the device, maybe something to do with either my phone being a UK phone or the fact that it has a different modem for the 5g version of it.
I think it's time I asked some people who know what they are talking about rather than trusting my own poor judgement :/ Does anyone know how I can fix the wifi and sim on this device now? I dont mind if it is on lineage os or if it goes back to oxygen os.
Device OnePlus 7Pro 5g | Model: GM1917 | Build: lineage_guacamole-userdebug 11 RQ3A.210905.001 10035588
The OnePlus 7 Pro 5G doesn't have working modem on custom ROMs past Android 10, and me and others efforts to get it working have failed. This is due to different modem and partitions. You also cannot flash the international firmware on it. This will most likely break modem even more. The best you can do is flash the EU5G firmware going by GM27BA. (Found here https://forum.xda-developers.com/t/...rint-oneplus-7-pro-5g-to-european-fw.4042583/). Also Android 11 is not out and probably will never be out. The source for the 7 Pro 5G isn't even fully out so building custom ROMs won't work
Thanks for the info and the link. I really appreciate it.
adriantechguy said:
The OnePlus 7 Pro 5G doesn't have working modem on custom ROMs past Android 10, and me and others efforts to get it working have failed. This is due to different modem and partitions. You also cannot flash the international firmware on it. This will most likely break modem even more. The best you can do is flash the EU5G firmware going by GM27BA. (Found here https://forum.xda-developers.com/t/...rint-oneplus-7-pro-5g-to-european-fw.4042583/). Also Android 11 is not out and probably will never be out. The source for the 7 Pro 5G isn't even fully out so building custom ROMs won't work
Click to expand...
Click to collapse
So if I were to go back to stock oxygen os would that fix my modem alone or will I need to fix the firmware separately since I flashed the global firmware over the top?
mansguiche said:
So if I were to go back to stock oxygen os would that fix my modem alone or will I need to fix the firmware separately since I flashed the global firmware over the top?
Click to expand...
Click to collapse
You can try. I bet it'll probably fix it
adriantechguy said:
You can try. I bet it'll probably fix it
Click to expand...
Click to collapse
Done! Just going through android initial setup now but it is registering my sim and wifi. You absolute legend. Thank you so much for your help.
Try YAAP custom ROM , works brilliantly
Hello, I had bought a tablet from Lenovo previousely, being Lenovo P11 which has Sm6115 qualcomm.
They did release the kernel source but for an old version of the oem firmware. As a result, it is missing drivers for newer variant of machines (They have different panels and touchscreens on newer variants) and as a result the touch screen does not work for the machine I own (Wifi variant)
Luckliy the "5G" variant of the tablet has SD765 in it but has the same touch panel (Novatek NT36523) so I tried to copy that driver to my device's kernel and I'm unable to fix this error while compiling.
This is the repo for my kernel (Yes, I did not restore git history yet because I'm lazy) : https://github.com/HexagonWin/m11_row_kernel_temp
And this is the error message : https://pastebin.com/90XAsb2X
This is 5g variant kernel : https://download.lenovo.com/consumer/mobiles/tb-j607z_opensource_tb-j607z_s130035_210706_row.tar.gz
The weird thing is that the 5g variant kernel builds properly with that same touch panel driver included in defconfig. The defconfig I'm using for my kernel tree right now is "arch/arm64/configs/m11_defconfig". Could somebody please see what is causing the issue? I'm not able to understand.. Thanks. (Including -fPIC in root makefile's KBUILD_CFLAGS didn't help.)
Correction: It's bengal (Snapdragon 662), not sm6115.
Edit: Ok it seems that sm6115 is actually bengal
You've taken the driver from a kernel source for Android 11. So either backport it or merge the kernel with an Android 11 CAF tag and use the kernel on the Android 11 firmware.
adazem009 said:
Correction: It's bengal (Snapdragon 662), not sm6115.
Edit: Ok it seems that sm6115 is actually bengal
You've taken the driver from a kernel source for Android 11. So either backport it or merge the kernel with an Android 11 CAF tag and use the kernel on the Android 11 firmware.
Click to expand...
Click to collapse
My device is not upgrade to lenovo's android 11 fw. Did you upgrade your device?
I did not upgrade yet because i was uncertain if lenovo's android 10 oss kernel would even boot on the android 11 bootloader, and i was unsure if i can revert to the android 10 firmware later on.
it can be because the android 11 caf tag's changes aren't merged, i'm not sure.. maybe we can try loading the lenovo's android 10 firmware nvt kernel module using something like ghidra and compare that with the module that gets built with the nvt driver code from another device's android 11 kernel
LegendOcta said:
My device is not upgrade to lenovo's android 11 fw. Did you upgrade your device?
I did not upgrade yet because i was uncertain if lenovo's android 10 oss kernel would even boot on the android 11 bootloader, and i was unsure if i can revert to the android 10 firmware later on.
it can be because the android 11 caf tag's changes aren't merged, i'm not sure.. maybe we can try loading the lenovo's android 10 firmware nvt kernel module using something like ghidra and compare that with the module that gets built with the nvt driver code from another device's android 11 kernel
Click to expand...
Click to collapse
Yes, I've already upgraded, but it's possible to downgrade. However, Lenovo didn't release any complete firmware package. Android 10 will boot after downgrading, but OTA updates won't work anymore. Also downgrading works only with a specific firmware package. I'll send the package ID later...
adazem009 said:
Yes, I've already upgraded, but it's possible to downgrade. However, Lenovo didn't release any complete firmware package. Android 10 will boot after downgrading, but OTA updates won't work anymore. Also downgrading works only with a specific firmware package. I'll send the package ID later...
Click to expand...
Click to collapse
Hmm, interesting.
As my device's still on Android 10, maybe I should backup the partitions (manually via dd?) and try using them later..?
Honestly I'm a bit worried about doing anything that can't be reverted because unlike my other Android-based devices this one is something i've actually bought, lol.
So, the kernel you built from your modified tree (with prima wlan included) boots on the Android 11 bootloader/firmware? The subversion of the Android 10 is significantly lower than the Lenovo Android 11 kernel AFAIK, not sure if it's just the CAF patches or anything else..
LegendOcta said:
Hmm, interesting.
As my device's still on Android 10, maybe I should backup the partitions (manually via dd?) and try using them later..?
Honestly I'm a bit worried about doing anything that can't be reverted because unlike my other Android-based devices this one is something i've actually bought, lol.
So, the kernel you built from your modified tree (with prima wlan included) boots on the Android 11 bootloader/firmware? The subversion of the Android 10 is significantly lower than the Lenovo Android 11 kernel AFAIK, not sure if it's just the CAF patches or anything else..
Click to expand...
Click to collapse
No, I haven't been able to run it on Android 11, only Android 10. Also the device doesn't use prima wlan but a kernel module in /vendor/firmware, it wasn't working because of kernel module signature checks.
adazem009 said:
No, I haven't been able to run it on Android 11, only Android 10. Also the device doesn't use prima wlan but a kernel module in /vendor/firmware, it wasn't working because of kernel module signature checks.
Click to expand...
Click to collapse
Then, even if we make the oss kernel working most people won't be able to benefit from it as most people already have android 11 running.
Maybe we might go with the mainline route instead, I remember hearing that people got the mainline kernel booting on sm6115, was on a oneplus device probably..
Any news?
Hello all, after lurking here for a while, I found something that's making me post.
I have a carrier locked OP9. I just received the update to Android 12, and it has broken critical features. (Particularly not being able to stop apps from being closed accidentally!)
I have looked at Lineage OS in the past, and the process to get the LE2117's bootloader unlocked was... complicated.
However, while trying to fix other problems, rooting around in the developer options, I noticed that "unlock bootloader" was actually toggleable!
I think I have an unlocked bootloader now, but it's on android 12, and all the guides for rooting and installing a custom MOD for this phone say you must revert to android 11 before anything else.
So what now? Am I waiting for lineageOS 19 to come out, because that's the one based on android 12? I'm new to custom roms, and don't get the coding side of how all this works. (But I'm pretty determined to figure this out.)
Thanks for any help or advice you've got!
each stock update has a new firmware right now atleast all the roms are based on a11 latest firmware im not sure since oneplus got a12 if roms will switch to the newer firmware here is to hoping!
Gotcha, thanks. So waiting for lineage 19 it is, it sounds like, since that one is based off android 12.
dark_sable said:
Gotcha, thanks. So waiting for lineage 19 it is, it sounds like, since that one is based off android 12.
Click to expand...
Click to collapse
I am pretty sure there is root for 12. All you need to do is dump the payload from the 12 update OnePlus let's loose, and patch it with magisk and flash it via fastboot. Via bootloader it is easy I am using a TMobile OnePlus 9. All you need to do is revert back to 11 via a msm tool. There is a post here for that. After downgrading to unlock your bootloader is easy only takes time. There is a post for it I don't remember all the details but all you have to do is get you imei code and email OnePlus. Soon they will sent you a code to fastboot flash to unlock the bootloader. After that most of these 12 work for us on our model phone. I am using evolution x. It tells me every day I can go to 12 .
funkybear34 said:
each stock update has a new firmware right now atleast all the roms are based on a11 latest firmware im not sure since oneplus got a12 if roms will switch to the newer firmware here is to hoping!
Click to expand...
Click to collapse
Yes yes they do.
I've run into this same issue with wanting to use a Custom ROM. I have the T-Mobile version on A12 and it's now rooted. Another user shared the patched image file with me. I flashed it with fastboot boot boot.img then direct installed through Magisk to gain root. But all the custom roms here require A11 downgrade through the MSM tool and you have to use an MSM tool for T-Mobile, which was shared with me and explained but I'm not willing to downgrade. Until a custom ROM releases that I can flash on top of A12 I won't use it. I've had bad experiences with MSM tool to recover from brick and didn't succeed and had to send back to OnePlus for repair.
JimmyL216 said:
I've run into this same issue with wanting to use a Custom ROM. I have the T-Mobile version on A12 and it's now rooted. Another user shared the patched image file with me. I flashed it with fastboot boot boot.img then direct installed through Magisk to gain root. But all the custom roms here require A11 downgrade through the MSM tool and you have to use an MSM tool for T-Mobile, which was shared with me and explained but I'm not willing to downgrade. Until a custom ROM releases that I can flash on top of A12 I won't use it. I've had bad experiences with MSM tool to recover from brick and didn't succeed and had to send back to OnePlus for repair.
Click to expand...
Click to collapse
It amazes me how many people have problems with the MSM Tool. I was afraid I was going to have problems after reading all the issues people have had and had zero and I've used it twice. Both times I just put the phone in EDL and connected it to the USB-C port on my tower. Windows 11 surprisingly didn't even give me any issues.
EtherealRemnant said:
It amazes me how many people have problems with the MSM Tool. I was afraid I was going to have problems after reading all the issues people have had and had zero and I've used it twice. Both times I just put the phone in EDL and connected it to the USB-C port on my tower. Windows 11 surprisingly didn't even give me any issues.
Click to expand...
Click to collapse
I can't get my phone to go into EDL mode. Ever. Took every suggestion I've read. It just never went into EDL mode
JimmyL216 said:
I can't get my phone to go into EDL mode. Ever. Took every suggestion I've read. It just never went into EDL mode
Click to expand...
Click to collapse
What worked for me was shutting the phone off, removing my case, holding both volume up and down, then plugging the phone in. The screen won't show anything, you have to look at the MSM Tool and see that it's connected to know you did it right. Both times I tried it worked perfectly.
You can also use adb reboot edl if you can get the thing to boot and have USB debugging turned on.
Hey guys all good?
I got my hands on an A53 already on Android 13 (U.I 5.1), then I unlocked the bootloader, rooted, magisk working but then I decided to downgrade from 13 to 12 because of a few things
I tried via Odin (13.14.4 and 13.12.7) and both didn't work the first odin it fails the flashing and the second pass but it didn't flash the whole thing just reset the phone
any idea? or I'm now stuck with Android 13?
Cheers
From what I can find, Odin supposedly won't allow a downgrade if the boot loader version is lower.
That's just what people seem to say about Samsung devices and downgrading. I've never tried it and never will. Would immediately use multiple OS versions however if Android actually supported dual booting. Its fantastically messed up that it doesn't.
Not sure if TWRP will. Didn't look that one up. You didn't bring that one up but it might be a way to do it.
sandsofmyst said:
From what I can find, Odin supposedly won't allow a downgrade if the boot loader version is lower.
That's just what people seem to say about Samsung devices and downgrading. I've never tried it and never will. Would immediately use multiple OS versions however if Android actually supported dual booting. Its fantastically messed up that it doesn't.
Not sure if TWRP will. Didn't look that one up. You didn't bring that one up but it might be a way to do it.
Click to expand...
Click to collapse
Thanks for the reply. I was thinking something about that too. Not that the bootloader is lower but that it was modified (root) i guess
Unfortunately TWRP is not compatible yet with Android 13 UI 5.1 at least accordingly to this topic
So i guess I'm stuck for now
biustech said:
Thanks for the reply. I was thinking something about that too. Not that the bootloader is lower but that it was modified (root) i guess
Unfortunately TWRP is not compatible yet with Android 13 UI 5.1 at least accordingly to this topic
So i guess I'm stuck for now
Click to expand...
Click to collapse
You could flash a GSI image, but I guess that wouldn't be OneUI anymore
Hello you all hope you're having a good day, so no way to downgrade a53 5g from Android 13 to android 12 ??? I found some firmwares for Android 12 but the binary number is 4 and Android 13 is actually on binary number 5 , no way to do the downgrade with Odin?
I read somewhere that is not possible to flash a firmware with different binary number is it true ?? I would like to comeback to android 12 it's better