I don't understand why we should flash firmware.zip/radio.zip in many custom roms....
Mostly because without appropriate firmware, your phone security (i.e. lockscreen pin, pattern, password and fingerprint unlock) won't work. And the radios zips enables the ROM to use the radio hardware which basically makes phone calls happen. So, yes they are very important
You don't have to.
I didn't and everything works fine on Resurrection Remix.
Related
Hi,
I'm with Telus, and been running custom roms for a while now, without any problems... until now.
To make a long story short, I was stupid enough to let the Sprint customization run on the latest stock rom; from then on, I couldn't get any data connection from any custom rom I tried. All in all, a pretty common problem.
So, in order to fix the Sprint customization, I re-flashed the latest stock Telus rom, and that went great. Re-locked the phone, and re-flashed a custom rom (dcd 3.2.x, everytime with the Telus carrier cab of course) believing that all would be working good now. But, I still couldn't get a data connection.
I flashed back the stock rom, and tested there if I could get the connection; lo & behold, the data connection actually works with the stock rom! I've done that pattern a couple times now, and everytime I flash a custom rom, I can't get data to work, even tough it seems to work all right when using the stock rom.
I never seen references of that problem when data only works with the stock rom; any idea what I can do to repair the data connection for custom roms? Thanks a lot.
install the Telus carrier cab. thats the only reason why u dont get data. I'm with Telus as well and run the latest from DCD w/no problems. Make sure u have the latest or min. req. radio.
This has been checked and done over and over. I always install the telus cab. I tried installing it multiple times. I tried installing an older one. I tried an older radio. I tried a hard reset.
Sorry, but I really need something not as obvious as installing the carrier tab to fix the problem.
To make a long story short, I was stupid enough to let the Sprint customization run on the latest stock rom; from then on, I couldn't get any data connection from any custom rom I tried. All in all, a pretty common problem.
So, in order to fix the Sprint customization, I re-flashed the latest stock Telus rom, and that went great. Re-locked the phone, and re-flashed a custom rom (dcd 3.2.x, everytime with the Telus carrier cab of course) believing that all would be working good now. But, I still couldn't get a data connection.
Click to expand...
Click to collapse
There have been several threads and posts regarding your specific issue. Please search a little more next time, because you would have found the answer.
You will not get data working again until you get a DMU reset from your carrier. The Sprint customizations overwrote your DMU keys and they need to be reset. Flashing the stock rom refurbishes your PRI and gets the rest working fine, but for data this is the ONLY way, next to swapping your phone out for a new one.
But why does my data works with the stock rom if my DMU is wiped?! That's what I don't understand. And like I said, it's consistent; I'm on the stock rom, data works. I flash a custom rom (obviously unlocking and flashing a new radio too), install the carrier cab, data doe not work. I flash back the stock rom, data works. How come?
edit: I re-read a good bunch of the threads speaking about letting the customization for another carrier run, and not once did I see the same problem that I have; that is, that data is working with the stock rom, but not with a custom one. Would it be particular to Telus? And don't tell me I'm not installing the carrier cab when I go custom.
Agarwal said:
But why does my data works with the stock rom if my DMU is wiped?! That's what I don't understand. And like I said, it's consistent; I'm on the stock rom, data works. I flash a custom rom (obviously unlocking and flashing a new radio too), install the carrier cab, data doe not work. I flash back the stock rom, data works. How come?
edit: I re-read a good bunch of the threads speaking about letting the customization for another carrier run, and not once did I see the same problem that I have; that is, that data is working with the stock rom, but not with a custom one. Would it be particular to Telus? And don't tell me I'm not installing the carrier cab when I go custom.
Click to expand...
Click to collapse
I had the same problem as you man, except with verizon wireless. If you've followed all the steps (i.e flashed to stock, and then flashed the new radio without letting customizations run) then there's only one thing left to do which fixed my problem. Call up Telus and have someone remove your Data feature, and to put on Pay per KB/MB. It should THEN work, because the DMU is now reset. So after it's removed, give it a whirl to google.com or whatever. Hang up, and call back. Ask them to add the data plan again. Data should now work for you
Let me know if the problem persists!
I'll call Telus in the next few days and try to make my way to a DMU reset. I'll post the results once it's done.
FIXED, and WITHOUT getting my DMU reset. I simply installed that rom:
http://forum.xda-developers.com/showthread.php?t=364157
with radio 3.27, and data worked. This was the first time since the Sprint customization that I could get data working on a non-stock rom. I then proceeded to install a newer radio and the latest dcd. Works like a charm
Told you guys a DMU reset didn't make sense since data was working with the stock rom!
After I try upgrading the ROM everything seems to work great (GPS, WiFi, stability, etc) except the phone part (phone radio? Sorry I don’t quite know the terminology). Here is kind of the “events” as they happened
Recently
Working phone (i9100)
upgraded/flashed to newer Resurrection Remix ROM
phone asking for sim unlock code (but can see mobile operators, just won’t connect)
tried Galaxy S Unlock and it worked (kinda, had to run Galaxy S Unlock everytime I rebooted phone)
Now
Upgraded to AOKP ROM
Phone asked to unlock sim again
This time Galaxy S Unlock didn't work
Went back to really old backup (year ago)
It asked me for SIM unlock code
I ran Galaxy S Unlock and it worked (even after reboots)
Tried restoring certain parts (advance restore in CWM)
nothing worked.
Restored to really old backup again
didn't ask for sim unlock code.
Tried/flashed the newst RR again, and now back to Phone (calls) not working again
I am stumped. I would like to upgrade to one of AOKP's or RR's newer ROMs but can't understand why it doesn't work or how to resolve this. Any suggestions would really be appreciated!
Cheers,
-Gaiko
gaikokujinkyofusho said:
After I try upgrading the ROM everything seems to work great (GPS, WiFi, stability, etc) except the phone part (phone radio? Sorry I don’t quite know the terminology). Here is kind of the “events” as they happened
Recently
Working phone (i9100)
upgraded/flashed to newer Resurrection Remix ROM
phone asking for sim unlock code (but can see mobile operators, just won’t connect)
tried Galaxy S Unlock and it worked (kinda, had to run Galaxy S Unlock everytime I rebooted phone)
Now
Upgraded to AOKP ROM
Phone asked to unlock sim again
This time Galaxy S Unlock didn't work
Went back to really old backup (year ago)
It asked me for SIM unlock code
I ran Galaxy S Unlock and it worked (even after reboots)
Tried restoring certain parts (advance restore in CWM)
nothing worked.
Restored to really old backup again
didn't ask for sim unlock code.
Tried/flashed the newst RR again, and now back to Phone (calls) not working again
I am stumped. I would like to upgrade to one of AOKP's or RR's newer ROMs but can't understand why it doesn't work or how to resolve this. Any suggestions would really be appreciated!
Cheers,
-Gaiko
Click to expand...
Click to collapse
Thoughts? Anyone? Please
Use a ROM Wipe/Nuke script, do a clean install of the ROM and use GalaxSim Unlock app. :good:
immortalneo said:
Use a ROM Wipe/Nuke script, do a clean install of the ROM and use GalaxSim Unlock app. :good:
Click to expand...
Click to collapse
Thanks for the response immortalneo, i guess I have a question regarding that. Before I flash the new ROM (while booted in recovery mode in CWM) I usually do the wipe cache/factory reset.
Should I perhaps be doing a wipe davlik and wipe partition cache also?
people
i have s2
imei lost no backup i get it this way
no chance for repair
if its hardware
what can do
gaikokujinkyofusho said:
Thanks for the response immortalneo, i guess I have a question regarding that. Before I flash the new ROM (while booted in recovery mode in CWM) I usually do the wipe cache/factory reset.
Should I perhaps be doing a wipe davlik and wipe partition cache also?
Click to expand...
Click to collapse
That is what a ROM nuke/wipe script does. It wipes everything and provides a clean slate for your new ROM. Look for hawkerpaul's scripts.
gaikokujinkyofusho said:
After I try upgrading the ROM everything seems to work great (GPS, WiFi, stability, etc) except the phone part (phone radio? Sorry I don’t quite know the terminology). Here is kind of the “events” as they happened
Recently
Working phone (i9100)
upgraded/flashed to newer Resurrection Remix ROM
phone asking for sim unlock code (but can see mobile operators, just won’t connect)
tried Galaxy S Unlock and it worked (kinda, had to run Galaxy S Unlock everytime I rebooted phone)
Now
Upgraded to AOKP ROM
Phone asked to unlock sim again
This time Galaxy S Unlock didn't work
Went back to really old backup (year ago)
It asked me for SIM unlock code
I ran Galaxy S Unlock and it worked (even after reboots)
Tried restoring certain parts (advance restore in CWM)
nothing worked.
Restored to really old backup again
didn't ask for sim unlock code.
Tried/flashed the newst RR again, and now back to Phone (calls) not working again
I am stumped. I would like to upgrade to one of AOKP's or RR's newer ROMs but can't understand why it doesn't work or how to resolve this. Any suggestions would really be appreciated!
Cheers,
-Gaiko
Click to expand...
Click to collapse
it sounds like your RIL is incorrect, try this: http://forum.xda-developers.com/showthread.php?t=1187681
Hope this helps
I currently have an locked, unrooted Z5C.
I've always rooted my old phones because I liked trying out new features and hopefully get a better faster phone. However, certain things are critical to me (Phone calls, Camera, GPS, Data/Wifi).
To start with, I basically hope to be able to get some software requiring root to work (Gsam Battery root companion, xposed, cpu gov control) and see if there are some bug fixes (like volume boost). Then any improvements to speed (ie. debloating, etc). Then any added functionality like improved GUIs, better ability to backup.
I'm trying to decide if I should go ahead and root or keep waiting for custom ROMs to mature.
As I understand it, there is a procedure to unlock your phone, root, then load replacement DRM keys. What are my options after doing this? Looking thorugh threads, it seems like these are my options:
1. Install back the stock rom. Will this give me identical functionality to what I have now but with the ability to run root-apps?
2. Install a custom ROM. I basically see CM13, XPower, OMNI. If I use a custom ROM, do I loose access to all sony software? (ie. camera app, advanced camera features)
2a. CM13, I see there is currently a bug with videos and bluetooth so that is prob a dealbreaker for me at this point.
2b. XPower ROM. I've been trying to determine what the known bugs for this ROM are.
2c. OMNIROM seems to have issues with the camera so that's prob a dealbreaker as well.
Am I missing any other options?
eng3 said:
I currently have an locked, unrooted Z5C.
I've always rooted my old phones because I liked trying out new features and hopefully get a better faster phone. However, certain things are critical to me (Phone calls, Camera, GPS, Data/Wifi).
To start with, I basically hope to be able to get some software requiring root to work (Gsam Battery root companion, xposed, cpu gov control) and see if there are some bug fixes (like volume boost). Then any improvements to speed (ie. debloating, etc). Then any added functionality like improved GUIs, better ability to backup.
I'm trying to decide if I should go ahead and root or keep waiting for custom ROMs to mature.
As I understand it, there is a procedure to unlock your phone, root, then load replacement DRM keys. What are my options after doing this? Looking thorugh threads, it seems like these are my options:
1. Install back the stock rom. Will this give me identical functionality to what I have now but with the ability to run root-apps?
2. Install a custom ROM. I basically see CM13, XPower, OMNI. If I use a custom ROM, do I loose access to all sony software? (ie. camera app, advanced camera features)
2a. CM13, I see there is currently a bug with videos and bluetooth so that is prob a dealbreaker for me at this point.
2b. XPower ROM. I've been trying to determine what the known bugs for this ROM are.
2c. OMNIROM seems to have issues with the camera so that's prob a dealbreaker as well.
Am I missing any other options?
Click to expand...
Click to collapse
If you have no "need" to root I'd hold off. There are no custom Roms that are functional as a daily driver yet. On the contrary the OEM ROM has so many bugs it needs to be rebooted a few times a day and wiped every few weeks so you don't have much to lose!
Here's a list of my mods to lollipop that I run:
http://forum.xda-developers.com/z5-compact/themes-apps/post-setup-apps-tweaks-t3349010
Hi,
I am running RR 5.8.3, v. from 23-04-17.
I was forced to set fluencetype for the past few flashes to null or something, because otherwise I did not have sound during calls.
Right now the call quality is unbearably bad. It was not THAT bad on older ROMs, before I had to disable this fluence-thingie.
I want to upgrade the ROM, but what else am I supposed to improve the voice quality? I could not find a decent source.
Factory reset -> VoLTE patch -> RR ROM -> GAPPS?
Anything else? Some people wrote "updade your firmware" - how am I supposed to interpret it? Install MIUI Rom? So, like flash it from TWRP and replace it with RR 2 minutes later? I am alergic to MIUI.
This topic kind of explains it, but links are down and content might be outdated:
https://forum.xda-developers.com/redmi-note-3/how-to/android-n-permanent-volte-fix-10000-t3541922
Up
Up.
Right now I am stuck on a bootloop with rom's logo. I can access TWRP and flash stuff just fine, but I cannot load the system. Restoring from backup has failed.
I have installed 7.7.7 firmware - https://www.androidfilehost.com/?fid=673368273298969813
and booted to the system. It did not recognize my PIN and locked my card. Unlocked it with PUK on another device, but still the same.
Flashed newest RR with GAPPS and reflashed the firmware. Bootlooping begun.
Tried different ROMs, tried a different firmware - https://www.androidfilehost.com/?fid=673368273298969055
What should be the "next step"?
I was able to fix it, but man this was my last flash of this device. My next step was to brick the device, had to start from stratch after that. Never had so many different issues... I will rot on current ROM till Pixel 2 arrives.
Hi everyone. this is my very first post. I'm an Owner of a Redmi 6a (Cactus) Running Lineage OS 17.1 Unofficial (20200727) and I'm having some issues with the from so. first, I would like to know which Custom ROM Its better for this model now in 2022. more stable and updated. and also. if I can change the custom ROM to another without problems, just wiping some things ( I have TWRP and Bootloader unlocked already), or I have to get back to MIUI again.
I'm seeking something with the highest android version available for this model without problems like slow charging. camera stops or issues with daily usage, I would like to get my phone a little more powerful again.
Any suggestions, and comments, are well received by me.
Thanks to everybody
welcome to the dark side
so at the beginning i just tested some of the available costom roms, each for a few days (like go shopping) to get to know the functions and to see if they are stable (stable enough - because you can't find all bugs in short time). i am now using LineageOs but this is a personal preference. maybe i should go "shopping" again to see how the other costom roms have evolved over the past two years. as long as i did this testing i flashed all the roms "dirty", this means as you said, just wiping/formatting in twrp and flash new rom but as soon as i left testing and decided to use a rom for a longer period of time i did a "clean" flash. this means flash stock rom again (be careful to don't lock your bootloader again, its preselected in miflash unlock tool), then boot system, enable adb debugging, flash twrp, flash costom rom. i would say from experience that if you do a dirty or even clean flash, lets say you do it 10 times in a row, you will not always get the same result. maybe sometimes in LineageOs (at some devices) the radio is missing, sometimes it's not. sometimes you have a bug with a camera, sometimes you don't. flashing clean should reduce the error rate. this in the first place and the different region versions make it hard to help someone who has a device specific - rom specific - one in a hundred times bug - they need some help with.