Hello!
I have a Redmi Note 6 Pro, which i wanted to update to the latest baseband version (To be able to update Havoc Rom to the latest version, as well).
When i flashed latest version for my phone from xiaomifirmwareupdater.com, the screen started flashing, and touch detection was way off. I solved this by downgrading to an earlier baseband version, but i still want to update it, what can i do?
Another problem (or rather weird occurance) i found while looking into this, is that the "Model and Hardware"-section of my settings show my phone as a "Redmi Note 5". The weird thing is that i do 100% have a Note 6 Pro, i was worried for a while that i had misunderstood what kind of phone i bought, but after checking out both of them on Google images, i am sure What can lead to the phone showing the wrong hardware version like that?
I was thinking that these two things were related somehow (that i flashed the baseband for the wrong type of phone) but i am running an older version of the baseband for Note 6 Pro Tulip right now, and that works like a charm, so it's not that.
Thanks for any help you guys can provide, i really just want to upgrade my baseband & rom!
Related
Hi, my samsung omnia 7 (7740) has 0.628 as diagnosis menù. Interop unlock doesn't work with that. How can I update my diagnosis app?
If you read the Interop Unlock thread, I'm pretty sure it has directions. If you doa search, I *know* there are directions. If you instead make a new thread about it, you may get snarky answers.
That said, just un-installing Diagnostics from the app list, then re-installing it using the phone dialer, will install the new version (assuming your firmware has been updated to a new version since you installed it before).
Maybe i made a new thread because this doesn't work? I'm on 8107 now and diagnosis 0.628 installed again. I'm going back to 7740, but I don't find a solution to update diagnosis.
Well, if you want people to assume you've read the relevant info, it's a good idea to mention the things that somebody who has read it (and still can't update) would have told us, like:
A) The fact that you actually tried the standard update method already.
B) The steps you took and the result of them.
C) What firmware (*not* OS, firmware!) version your phone has.
That said, if the standard method doesn't work for you, I can't really help here. You could try a custom ROM if nothing else is working, I guess...
Firmware : 2424.11.11.2
Hardware: 3.15.0.4
Radio : 2424.11.9.1
Hardware radio : 0.0.0.800
Bootloader : 5.11.1.8
SOC: 0.36.2.0
I don't like custom rom for now, it's v1 and still not full stable..waiting..
Hello everyone I wanted to test marshmallow so I decided flash xtra smoth rom by daniel84cs.as I am coming from lollipop so I flashed bootloader and radio of marshmallow but then I stuck into bootloop somehow I managed to get my backup restored now I am back to lollipop as I have done a factory rest before restoring so I should need to flash lollipop bootloader and radio again or I am good to go?thanks
Sent from my Nexus 5 using Tapatalk
I had this question as well. i have been running a Kit Kat rom for the past year and am also going to be trying Marshmallow in the next couple days. I wondered whether i would need to 'downgrade' my radio and bootloader if i went back to Kit Kat or to Lollipop.
Along these same lines, I was wondering whether if I didn't like Marshmallow and rolled back to a different android version by flashing a TWRP backup image, would my phone still have the Marshmallow radio and bootloader installed after?
What effects might an out of date or future version bootloader have on the system?
So i found an answer to this in a thread about the unofficial Chroma 6.0 ROM port to for the N5 on the Chroma google community. Here is the post, the relevant question and answer is in the comments. So keep in mind this isn't official info from google but it's more useful than anything i've found otherwise. https://plus.google.com/+KaioDuarteds/posts/EmTVqmPr7ew.
TLR: Tim Seidler says "Yes, you can go back to Lollipop even with the new Marshmallow bootloader and radio."
I did a bit more research on bootloaders too....my understanding is that the bootloader is a small peice of software that starts the phone and shows it where to find the kernel and OS so that can boot up properly. This makes me think that a much older bootloader might cause issues if it were 'pointing' to the wrong part of the phone. If the location of things has changed around in a newer version, the phone might not be able to get the main system running and therefore wouldn't be able to boot. I guess it would depend on how different the bootloaders were between say version 4.x and 6.x, etc.
Having the wrong radio seems less risky. The radio is the modem, it is in charge of handling internet and cell signal connections. The wrong radio might not be able to connect to wifi or cell networks, or might connect poorly, but it shouldnt brick the phone. It seems pretty easy to flash different radios...back when i had a galaxy S2 i sometimes had to try different radios when i installed a new ROM (that had the wrong radio pre packaged in it) because some radios wouldn't pick up my cell provider very well. But i used to flash many different radios (for my device version) without issue. all that changed was the number of bars of signal i got.
The bootloader, when unlocked, causes my phone to freeze like crazy. I've tried so many different tools to get to the right one, but it never seems to be working right. There are a lot of custom roms but I can't use them thanks to this problem. Could someone try and suggest which tool I should use based on the device info I have on my phone?
It's a black Zenfone 5 a501cg. I bought it around May/June, 2015. It came with a Kitkat firmware, not sure which. What else.... a WW SKU.
Any help would be appreciated. Also, if there are any who faced this problem and got it solved, help me out here.
Hello Everyone!
So today something really interesting happened with me...... I'm feeling okay but i'm kinda nervous too.
I had rooted my phone earlier and flashed Lineage OS but i was encountering lots of problems so i tried to flash phone's firmware with odin.
My phone was Samsung Galaxy On7 Pro. I installed a firmware file and flashed it. But unfortunately, the firmware was of Samsung Galaxy On7 not Samsung Galaxy On7 Pro. When, i installed it, i encountered a DRK error! Then, it took me to Stock Recovery. From there, i wiped cache and internal storage and rebooted. It somehow worked very correctly. But now whenever i reboot my phone, i get Galaxy On7 logo not Galaxy On7 Pro. I don't know what happened but it's a MIRACLE of Android.........!!!!!!!
So, my queries are as follows:
Now, i'm stuck on Android Lollipop (5.1.1). There is a OTA update available within the system because it says its official now. What if i update? Will it even update? Or it will brick because phone model is different and firmware is diffrent?
Will it run smoothly in the situation where it is? (Note: I have not encountered any issues till now. Both Software and Hardware work well)
So, Miracles can happen in android world as happened with me.
Glad to hear you were able to unbrick your phone!
First a warning, I have no experience with your particular phone. But, I would think your update would go through. Usually the Pro and non-pro models are very similar and that is why your firmware worked. There might be some weird functionality in some areas like the camera or modems.
So, you can try the update. Worse case, you flash the On7 Pro firmware instead of the non-pro version again.
Well, the software updated and worked. No issues at all.
But i'm still confused how did it even work........
Anyway, i'm back to Marshmallow (6.0.1) again.
Everything works fine. I tested most things and all work correctly. I think Samsung just gave 8GB storage in non-pro version and 16GB in pro version and software is same xD
I also got new bootanimation and phone turn on sound from that
Moreover, i ordered a new Samsung M31 as i wanted more storage
But problems on older phone are also solved
Now, i will keep 2 phones
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