Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
shirazi15 said:
Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
Click to expand...
Click to collapse
I had this exact issue last week when flashing Kitkat AOSP ROM. Even restoring back to 4.3.1 no network connection was available, except for WiFi. Restoring your EFS will not even work. You just have to re-root your phone.
Not to worry, your phone is OK, perfectly OK. But just quite a bit of work needs to be done. Here: http://forum.xda-developers.com/showthread.php?t=2032849
1. Download original stock firmware for your country and telco
2. Download mode that firmware back to your phone using Odin
3. Download mode to install recovery, this will re-root your phone above steps will un-root your phone
4. Re-flash ROM of your choice, not Kitkat for now
After all i've gone through, and as much as i want to try Kitkat, i think this issue is recovery-related. Both TWRP and CWM needs updating for Android 4.4. I will wait until then.
All the best!
Gandicela said:
I had this exact issue last week when flashing Kitkat AOSP ROM. Even restoring back to 4.3.1 no network connection was available, except for WiFi. Restoring your EFS will not even work. You just have to re-root your phone.
Not to worry, your phone is OK, perfectly OK. But just quite a bit of work needs to be done. Here: http://forum.xda-developers.com/showthread.php?t=2032849
1. Download original stock firmware for your country and telco
2. Download mode that firmware back to your phone using Odin
3. Download mode to install recovery, this will re-root your phone above steps will un-root your phone
4. Re-flash ROM of your choice, not Kitkat for now
After all i've gone through, and as much as i want to try Kitkat, i think this issue is recovery-related. Both TWRP and CWM needs updating for Android 4.4. I will wait until then.
All the best!
Click to expand...
Click to collapse
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
shirazi15 said:
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
Click to expand...
Click to collapse
Mate, firstly this is the hard way of recovering from "Unknown Baseband" issue. Finally the simple solution was only to download and install an app called SELinux Mode Changer from PlayStore. Then using that app, change SELinux from Enforcing to Permissive resolved everything related to IMEI, EFS, and Unknown Baseband. So hard way I did; i didn't know any better then.
By the way the link is correct. Start from the procedure from the line that says "Installation Instruction [Mobile odin is now have support for NOTE2]"
You must be in download mode (Vol Down, Home, & Power button all pressed together) to flash the Stock ROM using Odin. But where is your status now? If in recovery, can you re-install a ROM? If u r able to reboot back up to OMNI, just install the SELinux app and u will be good to go.
Cheers!
shirazi15 said:
Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
Click to expand...
Click to collapse
can you try what i did? http://forum.xda-developers.com/showthread.php?t=2567862&nocache=1
good luck.
"Just sharing my experience in solving this issue. Hopefully it will help solve those who have similar issues.
I flashed a file which messed up my EFS partition. I had a backup and tried to use the available programs to restore my EFS using my backup. None worked. I even brought it to the samsung store, but they said they would change the motherboard and reprogram, and replacement and service would cost more than half the cost of a new N7105. I purchased the phone in another country. The people who had stores to repair phones gave up on my phone. They also offered to replace the motherboard for US$175.00.
My phone was originally under a DMB2 rom (from Singapore I think). I flashed a DMC3 rom, and used this for five months, until i encountered the problem.
I initially gave up and got a note 3. But i could not believe the phone was junk and people in XDA (as I observed) do not seem to give up.
After two weeks, i found the solution below, which brought my phone to working condition.
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
2. I flashed a pit file using Odin. The pit file is found here:
http://forum.xda-developers.com/show....php?t=2137008
This restored the baseband. But IMEI was no longer NULL. However, it was still 0.
3. I downloaded and used the EFS Pro from this link:
http://forum.xda-developers.com/show....php?t=1308546
Before using EFS Pro, make sure you dial *#7284# and change the setting of Qualcomm USB Settings to
"RMNET + DM + MODEM"
I will not hurt your phone if you do, but EFS Pro will just not work. If you don't do this, the EFS Pro will display "Phone not responding" or something similar.
NOTE: I couldn't find the option with RMNET, but i used the option that also had an "RM*** + DM + MODEM".
After the phone is read, change back the IMEI to what it was originally.
Dial *#7284# again to change back to "MTP+ADB".
It's all working now.
Hope this is able to help someone. Now i have two working versions of Note.
Thanks to the authors of the program i used, and the people who uploaded the files used.
Cheers!
shirazi15 said:
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
Click to expand...
Click to collapse
karlonicolas said:
can you try what i did? http://forum.xda-developers.com/showthread.php?t=2567862&nocache=1
good luck.
"Just sharing my experience in solving this issue. Hopefully it will help solve those who have similar issues.
I flashed a file which messed up my EFS partition. I had a backup and tried to use the available programs to restore my EFS using my backup. None worked. I even brought it to the samsung store, but they said they would change the motherboard and reprogram, and replacement and service would cost more than half the cost of a new N7105. I purchased the phone in another country. The people who had stores to repair phones gave up on my phone. They also offered to replace the motherboard for US$175.00.
My phone was originally under a DMB2 rom (from Singapore I think). I flashed a DMC3 rom, and used this for five months, until i encountered the problem.
I initially gave up and got a note 3. But i could not believe the phone was junk and people in XDA (as I observed) do not seem to give up.
After two weeks, i found the solution below, which brought my phone to working condition.
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
2. I flashed a pit file using Odin. The pit file is found here:
http://forum.xda-developers.com/show....php?t=2137008
This restored the baseband. But IMEI was no longer NULL. However, it was still 0.
3. I downloaded and used the EFS Pro from this link:
http://forum.xda-developers.com/show....php?t=1308546
Before using EFS Pro, make sure you dial *#7284# and change the setting of Qualcomm USB Settings to
"RMNET + DM + MODEM"
I will not hurt your phone if you do, but EFS Pro will just not work. If you don't do this, the EFS Pro will display "Phone not responding" or something similar.
NOTE: I couldn't find the option with RMNET, but i used the option that also had an "RM*** + DM + MODEM".
After the phone is read, change back the IMEI to what it was originally.
Dial *#7284# again to change back to "MTP+ADB".
It's all working now.
Hope this is able to help someone. Now i have two working versions of Note.
Thanks to the authors of the program i used, and the people who uploaded the files used.
Cheers!
Click to expand...
Click to collapse
Nice, thanks!
For all others that might face "unknown baseband" with 4.3 to 4.4 flashing of ROMS, SELinux Mode Changer app from Playstore will fix that problem. Install the app and set SELinux from Enforcing to Permissive.
i hope your problem is fixed.
i'm not too familiar with CM roms, as i have been using stock since gingerbread. but you have to first do a full wipe before flashing from CM to stock. did you do that? perhaps you can go to recovery, do a full wipe, include Dalvik and Cache. Then go to bootloader and flash your rom.
by the way, my chipset is qualcomm yours may be exynos. if so, then i'm not confident about this solution because i have tried this several times, but only on note 2 LTE.
good luck!
my galaxy grand continue to reboot, i even flash the stock 4.1.2 and 4.2.2 firmware but still the phone reboots, it only reaches the wifi setup, then it restarts, please help.
chrowley said:
my galaxy grand continue to reboot, i even flash the stock 4.1.2 and 4.2.2 firmware but still the phone reboots, it only reaches the wifi setup, then it restarts, please help.
Click to expand...
Click to collapse
The information provided by you is not sufficient.There are some points i would like to know about.
Have u rooted your device?
Are you flashing through ODIN?
ROM version?
Did you make data wipe/ cache wipe before flashing over a previous firmware?
There are many threads associated with this.So please take a look over that.If you don't find answer then we are here to help you
ashwin77sgg said:
The information provided by you is not sufficient.There are some points i would like to know about.
Have u rooted your device?
Are you flashing through ODIN?
ROM version?
Did you make data wipe/ cache wipe before flashing over a previous firmware?
There are many threads associated with this.So please take a look over that.If you don't find answer then we are here to help you
Click to expand...
Click to collapse
yes sir rooted, i flash the firmware through odin, then i figured out that i have a backup so i restore it and its a yes it starts, , but the problem is sometimes it reboots and the screen is blinking sometimes, any solution for this sir? thanks in advance
chrowley said:
yes sir rooted, i flash the firmware through odin, then i figured out that i have a backup so i restore it and its a yes it starts, , but the problem is sometimes it reboots and the screen is blinking sometimes, any solution for this sir? thanks in advance
Click to expand...
Click to collapse
Thanks for Calling me "Sir". But seriously no need to say it. Say it to real developers.
Now coming to the topic,
For your information,keep in mind that when u flash the Official firmware through ODIN, You loose the root access.
Don't restore any backup. Just flash through ODIN. After flashing Wipe Cache and Data wipe is recommended too.
To gain the root access again you need to flash recovery from ODIN.
Other members looking at this this thread please correct me if i am wrong .I still not getting which backup the guy is talking about.
ashwin77sgg said:
Thanks for Calling me "Sir". But seriously no need to say it. Say it to real developers.
Now coming to the topic,
For your information,keep in mind that when u flash the Official firmware through ODIN, You loose the root access.
Don't restore any backup. Just flash through ODIN. After flashing Wipe Cache and Data wipe is recommended too.
To gain the root access again you need to flash recovery from ODIN.
Other members looking at this this thread please correct me if i am wrong .I still not getting which backup the guy is talking about.
Click to expand...
Click to collapse
oh sorry sir, i'll make it clear, my last firmware is 4.2.2 and my rom is GENNEXT, but when i encounter the problem, i tried to go back and flash the 4.1.2 stock firmware, then later i discovered that i have a backup from my previous rom(GENNEXT running 4.2.2 firmware) so i flash again the 4.2.2 stock firmware and flash the philz touch recovery, wipe data/factory reset, wipe cache and wipe dalvik cache then restore the back up, then my phone is restored but theres another problem sometimes the screen blinks and the phone reboots in a few minutes after the startup.
chrowley said:
oh sorry sir, i'll make it clear, my last firmware is 4.2.2 and my rom is GENNEXT, but when i encounter the problem, i tried to go back and flash the 4.1.2 stock firmware, then later i discovered that i have a backup from my previous rom(GENNEXT running 4.2.2 firmware) so i flash again the 4.2.2 stock firmware and flash the philz touch recovery, wipe data/factory reset, wipe cache and wipe dalvik cache then restore the back up, then my phone is restored but theres another problem sometimes the screen blinks and the phone reboots in a few minutes after the startup.
Click to expand...
Click to collapse
OK. Then it may be the problem with your GENNXT ROM cause the problem occured after restoring Backup.Try the fresh install of latest build of GENNXT rom.
ashwin77sgg said:
OK. Then it may be the problem with your GENNXT ROM cause the problem occured after restoring Backup.Try the fresh install of latest build of GENNXT rom.
Click to expand...
Click to collapse
i already tried it sir but it didnt solve the problem, it passes the setup but after a few minutes the phone reboots.
You might want to try one of the AOSP-based ROMs (CM11/Slimkat/Carbon/Omni/ProBAM) and see if it fixes the issue. If it still reboots even after installing one of those ROMs, then you probably has a faulty hardware. If it stops rebooting,then you probably has a corrupted installation of stock firmware...
Faulty hardware = get it to a service center, but be prepared to pay some bucks because you have already lost your warranty...
Corrupted stock firmware = try to flash the firmware again via Odin but DON'T RESTORE ANY BACKUP. If it still reboots, redownload the firmware package and reflash.
I'm not an expert, but I figured that your phone is already unusable by constant rebooting... let's just solve it by trial and error.
naufalhadyan said:
You might want to try one of the AOSP-based ROMs (CM11/Slimkat/Carbon/Omni/ProBAM) and see if it fixes the issue. If it still reboots even after installing one of those ROMs, then you probably has a faulty hardware. If it stops rebooting,then you probably has a corrupted installation of stock firmware...
Faulty hardware = get it to a service center, but be prepared to pay some bucks because you have already lost your warranty...
Corrupted stock firmware = try to flash the firmware again via Odin but DON'T RESTORE ANY BACKUP. If it still reboots, redownload the firmware package and reflash.
I'm not an expert, but I figured that your phone is already unusable by constant rebooting... let's just solve it by trial and error.
Click to expand...
Click to collapse
This is probably the best explained and most direct definition of what to do and what may be happening with our ever-rebooting Grands.... Thank you!!!
Had to create an account to thanks naufalhadyan
I was running on LineAgeOS 13.0 for a while until yesterday, when I went to install some random play store app and it crashed then went on a infinite rollercoaster with absolutely no fun making loops every time it got of the boot animation, did a factory reset, on the 2nd or 3rd app it crashed and looped, flashed another .zip with the rom, same, installed an RRemix on the same version (I like the 6) and when installing another random playstore it crashed the same way, now i'm on a AOSP 6.0 flashed from the recovery and so far i've been downloading the entire play store (just for kicks) and its smooth.
I don't use come to this troubleshooting section but on the last 24 hours there were some major bugs regarding endless loops, maybe a play store update came bugging our grand duos'? Is that even possible?
victorsmarotta said:
Had to create an account to thanks naufalhadyan
I was running on LineAgeOS 13.0 for a while until yesterday, when I went to install some random play store app and it crashed then went on a infinite rollercoaster with absolutely no fun making loops every time it got of the boot animation, did a factory reset, on the 2nd or 3rd app it crashed and looped, flashed another .zip with the rom, same, installed an RRemix on the same version (I like the 6) and when installing another random playstore it crashed the same way, now i'm on a AOSP 6.0 flashed from the recovery and so far i've been downloading the entire play store (just for kicks) and its smooth.
I don't use come to this troubleshooting section but on the last 24 hours there were some major bugs regarding endless loops, maybe a play store update came bugging our grand duos'? Is that even possible?
Click to expand...
Click to collapse
Even iam facing the same issue
phone reboots automatically and doesnt even start... infinite bootloop. Was working fine and suddenly this issue came up from nowhere(past 2 weeks) ..
Iam using Resurrection rom 5.7.4 (Marshmallow)
Damn I was on AICP 11, when this exact strange bootloop problem occurred for no rhyme and reason. I know the hardware is fine, the issue arises from installing apps from playstore, the moment it goes beyond a certain app limit in the device, it will start endless bootloop, I am sure this is Google's doing. Anyways this is not a hardware issue and I know more people will be coming here looking for answer to this issue. I have tried both the opengapps and deltagapps, same behaved this way, it never happened before and lately google have introduced one other app which is google's android instant app that will sit in your device, even though you need it not not. very well google for using our precious internal data to around 500Mb to 1Gb.
formating data partition solves this issue, temporarily but you lose your apps and data.
I had successfully avoided this issue when I stopped installing more apps on my device, It took me 2 tries and I found a perfect balance of 4-5 apps, it came crashing again when I tried installing the 7th app.
I don't know if other ROMs will be able to handle this bug, but I know it's time for me to look for another ROM, I was happy with AICP 11, for more than a year. Sad.
Reading about this issue, I came to know this is prevalent on all CM marshmallow based ROMs. So, going to flash Nougat or kitkat or the stock ROM should probably fix this.
Try a new battery.
Warning: This post is long, and probably full of grammatical errors due to my writing it late at night. a TL;DR is included at the bottom, but to fully understand my problem, I encourage you to read the whole post.
Hello, xdadevelopers community. I really need your help. So, recently I learned how to install custom ROMs myself and the experience has been really informative but also very struggling. To make a rather long story short, I bought a used G3 from my friend, had him root it, put a custom ROM on it, and everything was working fine. Only, that ROM was on Android 5.1.1, which was contemporary to when it was flashed. I wanted 6.0.1, so I went about getting it. I eventually got that up and running with Resurrection Remix, but the battery life was completely awful. Idle is okay, but using the device results in completely intolerable battery life. I asked Reddit what to do, and someone recommend crDroid for it's great battery life. I attempted to install that, and that's where I got the problems discussed in this post.
Post where I got the ROM and GApps from
Specific ROM and GApps I got:
- crdroid-6.0.1-20160118-vs985
- So I go the one for Android 6.0.1, and the most recent one at that, last updated on the 18th of January, for my G3 model the vs985
- for GApps, I selected "ARM", "6.0", and "Stock" from the menu
Could another problem be that the ROM is 6.0.1, and the GApps are 6.0? If so, open GApps version exists of 6.0.1.
Basically, I downloaded the two zip files, the ROM and the GApps. I then formatted my device, wiped it, did a real quick, skip through everything set-up of my current ROM, enabled USB debugging, copied the two zip files (ROM and GApps, both of which were inside a folder I made called ROM) onto my devices internal storage (I don't have an SD Card), and rebooted into recovery. I'm using Team Win Recovery Project (TWRP) v2.8.6.1 if that's helpful at all. Once in recovery, again I wiped the device (using the default wipe function in TWRP, then doing an advanced wipe and specifically selecting cache and Dalvik Cache, just to make sure), and went to flash the ROM, finally. I navigated to the ROM folder it was located it, selected it, and swiped to flash the ROM. I got the following in response:
Installing '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip'
...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Checking for BASEBAND version 35B
ERROR: It appears you are running an unsupported baseband. assert failed: h3.verify_baseband("35B:MPSS.DI.2.0.1.c1.13.4-00005") == "1"
E:Error executing updater binary in zip '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip'
Error flashing zip '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
So basically it failed to flash, apparently because of both an unsupported baseband version and a failure to execute a certain binary. Well, if you know how to fix the executing issue, that'd be great, although that's now what I'm focusing on here. I'm focusing on the baseband, because I believe that may be causing the failure to execute (although, as a newbie, I'm not sure if that's actually true). Apparently it was looking for version 35B, and that's not what I was running. When I set up my current ROM again just to be able to use the device, and checked for the baseband verion, it simply says "Unknown". Also, if you check out that link to the post above, it says:
We're mainly based on CyanogenMod so use custom kernels compatible with them!
Click to expand...
Click to collapse
. Well, I never installed a custom kernel, but I assume my friend did, because when looking at the kernel version on my phone it says:
3.4.0-CM-g74498f7
[email protected] #1
Mon Dec 14 09:48:16 EST 2015
Click to expand...
Click to collapse
.
I'm assuming if it was a non-custom kernel it would just have multiple numbers separated by periods, not have all that info, and it specifically says "CM" in there, so I assume that should work, but am not for certain.
Anyway, back to the baseband. It was looking for a baseband version 35B, which I apparently don't have. I have a few questions about this
1. How are you supposed to know your baseband version if your settings app returns "Unknown"?
2. How are you supposed to know what baseband versions work and what baseband versions don't work on the ROM you plan on flashing prior to doing so? I saw nothing about this from from start to failure to install.
3. If the ROM I intend to flash doesn't support my baseband version, can I install a custom baseband version?
I will admit, I don't even know what a baseband is, and I'm too tired to look it up as I write this.
So that's it. I realize this post is incredibly long but feel like if it was shorter, potentially important information would be nixed. I have a TL;DR below for your convenience, but as I just said, to get all the important information, read everything above, please.
TL;DR:
Tried to install a new ROM
Failed
Failing apparently due to unsuppported baseband version
I can't determine my baseband version b/c my settings app returns "Unknown""
If baseband is unsupported, how do I know which are?
Also apparently "E:Error executing updater binary in zip '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip' " is a thing. Caused by unsupported baseband version or entirely different problem all together?
Also maybe the ROM being 6.0.1 and the openGApps being 6.0 is a problem? If so, no openGApps 6.0.1 exist.
Please read the whole post to get all the detail needed.
NeatAndClean,
Thank you for providing the detailed information in this thread, so let's get to business.
First thing I want to straighten out is that you said your Baseband Version says "Unknown", i think you should check your IMEI information, if your IMEI is "null" then there is another problem to fix first.
If you have tried restoring from a backup after the "Baseband Unkown" issue and the Baseband Version still says "Unknown", then something happened whilst, or after you tried flashing CrDroid. At this moment I am not so knowledgeable about how to fix the Unkown Baseband issue, but it is a well known problem and usually coincides with the IMEI "null" issue. If you still are having that problem, I will try to find out how to fix it.
However, I will provide you with my full answer so this can hopefully get fixed at your preferred pace.
To start out, my questions are:
1. What ROM/Version of that ROM are you running right now? (I assume it is Resurrection Remix 6.0.1?)
2. Do you have a backup before trying to flash CrDroid? If so, I would suggest restoring from your backup to fix your "Settings Unkown" issue.
Once your Baseband "Unknown" problem is fixed, you can continue on to flash CrDroid (This time, it should work). Now I just downloaded the CrDroid zip file, that you used, on my PC. And just from opening it I can already tell that it is deeply based on CyanogenMod, but with some tweaks to make it CrDroid. Reason I mention this is because of this quote:
We're mainly based on CyanogenMod so use custom kernels compatible with them!
Click to expand...
Click to collapse
I'm not super knowledgeable on downloading Custom Kernels, but i do know that your Kernel:
3.4.0-CM-g74498f7
[email protected] #1
Mon Dec 14 09:48:16 EST 2015
Click to expand...
Click to collapse
is (I'm 99%sure) a CyanogenMod Custom Kernel, which comes when you flash a CM ROM.
Mine is:
3.4.0-CM-gc6520f1
[email protected] #1
Click to expand...
Click to collapse
and I'm running CyanogenMod 13, 6.0.1 on my vs985. Point is, you should be all set to flash CrDroid based on your Kernel.
Now, the "Unsupported Baseband" issue when flashing, at least CM based ROMs, is a known error recently. (In the past year I'd say) So the very common way to get around this, without having any issues, is to:
1. Go into your downloaded ROM zip, the zip you wish to flash, in your case it's crdroid-6.0.1-20160118-vs985.zip.
2. Extract the files into a folder (I'd recommend naming the folder the name of the .zip file, for ease in the end)
3. Open the extracted files folder
4. Open "META-INF" ==> "com" ==> "google" ==> "android"
5. Within that "android" folder, open "updater-script" file with Notepad, or a similar text editor.
6. Delete this line of code:
assert(getprop("ro.product.device") == "g3" || getprop("ro.build.product") == "g3" || getprop("ro.product.device") == "vs985" || getprop("ro.build.product") == "vs985" || abort("This package is for device: g3,vs985; this device is " + getprop("ro.product.device") + ".");
assert(g3.verify_baseband("35B:MPSS.DI.2.0.1.C1.13.4-00005") == "1");
Click to expand...
Click to collapse
7. You should be left with "ui_print("Target: lge/g3_vzw....." in your case.
8. Overwrite the edited "updater-script" back to it's directory (the android folder)
9. (Make sure you don't save it as a .txt file, it should still be a "File" (no extension))
10. Now go back to the "crdroid-6.0.1-20160118-vs985" folder after editing and saving "updater-script"
11. Select all the files/folders within, and add them to a .zip archive (Recommended by using WinRar)
12. You should end up with a .zip file visually identical to the original crdroid-6.0.1-20160118-vs985.zip, except this one has the edited "updater-script"
13. The edited one^ is the only one you need now, and is the one you will be flashing
14. Also, if you're curious I have done this many times with CyanogenMod, on vs985, and can assure you nothing bad will come of this... I assume the same is with CrDroid as it is deeply based on CM. (As long as you're "Unknown Baseband" problem has been fixed.
This procedure essentially gets rid of the Baseband/Model Check, ensuring a successful flash. Also as you can see in the code, it checks for the 35B:MPSS.DI.2.0.1.C1.13.4-00005 Baseband/Modem version, I believe "xdabbed" makes a flashable version of the 35B:MPSS.DI.2.0.1.C1.13.4-00005 Modem, which should eliminate the need to edit the updater-script. However, I strongly recommend to do the "updater-script" fix rather than trying to flash a different Baseband, as I have heard flashing a new Baseband can easily brick your phone, and you really do not need to do it.
I have Baseband: MPSS.DI.2.0.1.c1.13-00008, which does not match the "Baseband Check" and my ROM still works like a charm after the updater-script fix.
However, before you flash the edited crdroid-6.0.1-20160118-vs985.zip with your TWRP seperately, with the Marshmallow (6.x) ROMs right now, if you plan on using GApps you need to flash the ROM AND the GApps file at the same time in your custom recovery. Otherwise you will most likely get errors and you will need to re-flash the ROM and GApps.
Also maybe the ROM being 6.0.1 and the openGApps being 6.0 is a problem? If so, no openGApps 6.0.1 exist.
Click to expand...
Click to collapse
To answer this, no it is not a problem, you were correct.
1. The LG G3 is an ARM device
2. GApps only uses the first two digits in the OS version (i.e. 5.0.x or 6.0.x) (<==That "x" variable is the third digit in the OS version, and does not matter in GApps
3. All in all you have the correct version of GApps, no you just need to flash it at the same time as your edited ROM.
The procedure you did to flash the ROM was all good:
Basically, I downloaded the two zip files, the ROM and the GApps. I then formatted my device, wiped it, did a real quick, skip through everything set-up of my current ROM, enabled USB debugging, copied the two zip files (ROM and GApps, both of which were inside a folder I made called ROM) onto my devices internal storage (I don't have an SD Card), and rebooted into recovery. I'm using Team Win Recovery Project (TWRP) v2.8.6.1 if that's helpful at all. Once in recovery, again I wiped the device (using the default wipe function in TWRP, then doing an advanced wipe and specifically selecting cache and Dalvik Cache, just to make sure), and went to flash the ROM, finally
Click to expand...
Click to collapse
This is great, again the reason it didn't work was because of the mismatch in the Baseband Check, which shouldn't persist after following the instructions in the "updater-script" fix.
Anyway, back to the baseband. It was looking for a baseband version 35B, which I apparently don't have. I have a few questions about this
1. How are you supposed to know your baseband version if your settings app returns "Unknown"?
2. How are you supposed to know what baseband versions work and what baseband versions don't work on the ROM you plan on flashing prior to doing so? I saw nothing about this from from start to failure to install.
3. If the ROM I intend to flash doesn't support my baseband version, can I install a custom baseband version?
I will admit, I don't even know what a baseband is, and I'm too tired to look it up as I write this.
Click to expand...
Click to collapse
1. The Baseband Version is not supposed to state "Unknown", as i said in the beginning, this is a problem that happens sometimes, I am not sure why, or exactly how to fix it, but if you do some research I'm sure you will find something, I will also do some research so I can try to help you with that if it is not fixed by a Factory Reset or a Restore from Backup
2. The Baseband Version that a specific ROM calls for will be in that "updater-script" I was talking about, at least that's how it is for CyanogenMod based ROMs. I think your stock Baseband Version will work with any custom ROM, as long as it is a ROM made for your specific phone. That being said, I do think that the latest Baseband Version for your specific phone does improve Network, Cellular and GPS Connectivity, but again I do not recommend venturing there yet, until you have alot of background on it and can do it safely.
3. If the ROM you intend to flash doesn't support your Baseband, chances are the ROM is not made for your phone or you somehow have a Custom Baseband that is not made for your phone. I say that because even though you get that Baseband error when flashing CM based ROM, it is still supported, it's just that you do not have the "latest" Baseband Version I believe.
I do believe I have answered all of your questions, at least I hope so. I'm sorry that some things I could not answer in great detail, but I tried my best so that you could continue on enjoying your device. I also have the VS985 so I'm familiar with the device.
Summary:
1. Before anything try to Restore from Backup to fix the Baseband "Unknown" issue, as fixing this is priority. If that does not work I will try to find a fix online, or you can try to beat me to it.
2. Once that is fixed^ you can carry on with the "updater-script" fix i included.
3. Then flash the edited ROM and your 6.0, ARM OpenGApps at the same time (one right after another, without a Reboot in between)
4. Then you should honestly be all set
5. Your Kernel is all set for CrDroid
6. The GApps you said you downloaded is all good for the CrDroid version you downloaded
7. You could also try to flash back to vs985 stock (10B) this will hopefully give you your Baseband back if you still need it after Restoring from Backup
7. You should get no errors now! Yay. Now you can enjoy a Battery Optimized beautiful Marshmallow ROM
Click to expand...
Click to collapse
Please let me know if you have any confusion, I would be happy to provide you with clarification, screenshots etc.
I've run into a huge issue. My phone is semi-bricked now, and I don't know what to do. I was getting the baseband version error as well, and I removed the lines in the script and then it failed stating "wrong footer". I tried first installing CM, then like a fool, I installed Cyanogen Recovery over TWRP. Cyanogen Recovery can't do anything. But the install failed. I no longer have any version of Android on my phone, I can't install that baseband package with Cyanogen Recovery. Stock ROMs all come back "wrong footer" as well. I can't install anything. I have Fastboot/ADB installed. Please help!
Edit: I'm not sure if Fastboot is actually working. I can't get it to do anything. It just hangs on whatever command I give it, and it continues to hang until I unplug USB, then fails.
I've run into a huge issue. My phone is semi-bricked now, and I don't know what to do. I was getting the baseband version error as well, and I removed the lines in the script and then it failed stating "wrong footer". I tried first installing CM, then like a fool, I installed Cyanogen Recovery over TWRP. Cyanogen Recovery can't do anything. But the install failed. I no longer have any version of Android on my phone, I can't install that baseband package with Cyanogen Recovery. Stock ROMs all come back "wrong footer" as well. I can't install anything. I have Fastboot/ADB installed. Please help!
Click to expand...
Click to collapse
First off, in my response to @NeatAndClean I said to have the Baseband error fixed before proceeding, which is probably what caused your error.
For your Fastboot issue;
1. Make sure you are using the original Slimport cable (over-suggested, I know, just making sure)
2. Try USB 2.0 ports if you got them, if not, give this a shot forum.xda-developers.com/showthread.php?t=2256359
3. Try updating the phone's drivers
4. Otherwise, reinstall fastboot/ADB drivers or SDK Tools
5. Alternatively try this forum.xda-developers.com/showthread.php?p=48915118#post48915118
Assuming you have a VS985, here are stock IMG files:
forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
(If you do not have VS985 just find your Model's stock IMG files)
Here are commands you can use in fastboot once you manage to get it working, which will hopefully bypass your "Wrong Footer" issue. Obviously use your stock IMG files.
I would normally recommend flashing full stock TOT with LGFlashTool, but I'm not sure if it may worsen your Unknown Baseband issue (i.e. You may erase your IMEI if you Factory Reset when you have the Unknown Baseband problem) Here is everything you would need for the TOT Method: forum.xda-developers.com/showthread.php?t=2785089 - Also the old .dll needed for LGFlashTool probably won't work, so search LGUP_8974.dll and use that alongside the TOT instead) <== This should work if nothing else does, however, I don't think it will fix you "Unknown Baseband" but it may... I am not sure.
Finally, if you have ever made a previous backup, and still have it, if you restore from that your Baseband should re-appear and the error should fix itself. (I just figured you tried this already)
I once got the Unknown Baseband and IMEI - null issue, you could try to flash the stock Modem.img file for your phone, and try an IMEI injector program using the IMEI number in the battery compartment (Under the physical battery) But to fix mine I ended up calling the Customer Service and they eventually pushed an update file to my phone. I assume it was a Modem update of some sort, but it was a long time ago so I honestly don't remember.
I wish you good luck, as I know how frustrating these situations are. And keep in mind, I am only trying to help.
Please, to anyone experiencing the "Unknown Baseband Version" issue, focus on that before anything else, as you will most likely worsen your problem the more you do with the issue persisting.
Edit: Sorry, I didn't reach 10 posts yet, so you gotta drag 'n drop the links
Williquah said:
First off, in my response to @NeatAndClean I said to have the Baseband error fixed before proceeding, which is probably what caused your error.
For your Fastboot issue;
1. Make sure you are using the original Slimport cable (over-suggested, I know, just making sure)
2. Try USB 2.0 ports if you got them, if not, give this a shot http://forum.xda-developers.com/showthread.php?t=2256359
3. Try updating the phone's drivers
4. Otherwise, reinstall fastboot/ADB drivers or SDK Tools
5. Alternatively try this http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Assuming you have a VS985, here are stock IMG files:
http://http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
(If you do not have VS985 just find your Model's stock IMG files)
Here are commands you can use in fastboot once you manage to get it working, which will hopefully bypass your "Wrong Footer" issue. Obviously use your stock IMG files.
I would normally recommend flashing full stock TOT with LGFlashTool, but I'm not sure if it may worsen your Unknown Baseband issue (i.e. You may erase your IMEI if you Factory Reset when you have the Unknown Baseband problem) Here is everything you would need for the TOT Method: http://lgflashtool.net/index.php/tot-method/ - Also the old .dll needed for LGFlashTool probably won't work, so search LGUP_8974.dll and use that alongside the TOT instead) <== This should work if nothing else does, however, I don't think it will fix you "Unknown Baseband" but it may... I am not sure.
Finally, if you have ever made a previous backup, and still have it, if you restore from that your Baseband should re-appear and the error should fix itself. (I just figured you tried this already)
I once got the Unknown Baseband and IMEI - null issue, you could try to flash the stock Modem.img file for your phone, and try an IMEI injector program using the IMEI number in the battery compartment (Under the physical battery) But to fix mine I ended up calling the Customer Service and they eventually pushed an update file to my phone. I assume it was a Modem update of some sort, but it was a long time ago so I honestly don't remember.
I wish you good luck, as I know how frustrating these situations are. And keep in mind, I am only trying to help.
Please, to anyone experiencing the "Unknown Baseband Version" issue, focus on that before anything else, as you will most likely worsen your problem the more you do with the issue persisting.
Click to expand...
Click to collapse
Up until this point, I've only had the phone stock with the OTA updates from Verizon. It was updated the day I got the phone, so the baseband must be official, even if not supported by CyanogenMod. I wanna say it's 23B. I tried everything to get fastboot to work. I'm using the original cable that came with the phone "LG Electronics DC1501" plugged directly into a USB 2.0 port on my motherboard. If fastboot doesn't work, I can't flash imgs. An OS doesn't exist. I don't have a versatile recovery (Cyanogen Recovery might as well be stock). You say there's a chance TOT method will erase my IMEI, but you say there is an IMEI injector that can restore it, correct?
At this point, I'm at a loss. I really don't know what else can be done. I'm going to give the TOT method a shot. The website you linked has been suspended, so I'm following the 2015 updated method here: http://forum.xda-developers.com/showthread.php?t=2432476
---------- Post added at 09:09 AM ---------- Previous post was at 08:37 AM ----------
Knux Kitsune said:
Up until this point, I've only had the phone stock with the OTA updates from Verizon. It was updated the day I got the phone, so the baseband must be official, even if not supported by CyanogenMod. I wanna say it's 23B. I tried everything to get fastboot to work. I'm using the original cable that came with the phone "LG Electronics DC1501" plugged directly into a USB 2.0 port on my motherboard. If fastboot doesn't work, I can't flash imgs. An OS doesn't exist. I don't have a versatile recovery (Cyanogen Recovery might as well be stock). You say there's a chance TOT method will erase my IMEI, but you say there is an IMEI injector that can restore it, correct?
At this point, I'm at a loss. I really don't know what else can be done. I'm going to give the TOT method a shot. The website you linked has been suspended, so I'm following the 2015 updated method here: http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
OMG! It worked! My phone's still activated, so no problems with IMEI. I may be coming on kinda strong, but I LOVE YOU! I spent several hours yesterday, and I've been stressing about it ever since. I even put in a repair request with LG...now I can cancel that request. Thank you thank you thank you!
Knux Kitsune said:
OMG! It worked! My phone's still activated, so no problems with IMEI. I may be coming on kinda strong, but I LOVE YOU! I spent several hours yesterday, and I've been stressing about it ever since. I even put in a repair request with LG...now I can cancel that request. Thank you thank you thank you!
Click to expand...
Click to collapse
@Knux Kitsune Haha I'm glad that you finally got it working, I apologize about the problem with the link... I think I messed up all of the links in my response I'll fix those for the future. But again I'm just glad you got it working with no more problems, thanks for being so patient, XDA is like the best forum out there IMO.
Also, just curious, if you don't mind responding.. I was just wondering, did you use the KDZ method from the link you posted? Just want to know so that I know how many solutions there are for problems like these.
Anyway, enjoy your "new" phone lol, and be careful in the future because I know how painful these situations can be!
Glad you got it fixed!
:good::good:
Edit: The LGFlashTool link literally just got it's domain suspended like minutes after I posted it.. quite ironic.
Williquah said:
@Knux Kitsune Haha I'm glad that you finally got it working, I apologize about the problem with the link... I think I messed up all of the links in my response I'll fix those for the future. But again I'm just glad you got it working with no more problems, thanks for being so patient, XDA is like the best forum out there IMO.
Also, just curious, if you don't mind responding.. I was just wondering, did you use the KDZ method from the link you posted? Just want to know so that I know how many solutions there are for problems like these.
Anyway, enjoy your "new" phone lol, and be careful in the future because I know how painful these situations can be!
Glad you got it fixed!
:good::good:
Edit: The LGFlashTool link literally just got it's domain suspended like minutes after I posted it.. quite ironic.
Click to expand...
Click to collapse
I actually downloaded the KDZ, but I used the TOT method. I actually almost did it again, because in KitKat, my connection was very unstable, I did install the 35B baseband from XDABBEB, but that didn't fix the problem. I tried updating the firmware legitimately via LG Upgrade Assistant Utility (Verizon), but it kept giving an error everytime it got to 20%. I found no support online to get past this error, so I looked into stock ROMs and found XDABBEB (again) had built a flashable stock ROM for my phone, identical to what Verizon released last month, but with root access. I flashed TWRP 3.0 with Flashify, then flashed the ROM. The first time I flashed it, the phone showed that the phone service had stopped responding, a dialog box that only comes up once per cycle...super annoying. I managed to get back into Flashify and attempted installing the ROM again. I was actually prepared to do another TOT flash if it still had issues, but the second time wiping and flashing worked. My connection is solid, and I've had no errors (so far). It seems to run faster on Marshmallow than it did on Lollipop. It's pretty much the end result I was going for when I tried upgrading some 35 hours ago.
Update: Apparently, my baseband is fixed now. It did say Unknown before, even after flashing the 35B baseband from XDABBEB (initially anyways, reflashed after wipe just before flashing the ROM), but now it says "VS985-MPSS.DI.2.0.1.c1.13.4-00005-M8974AAAAANPZM-1"....so that's...good?
*Solution*
Knux Kitsune said:
I actually downloaded the KDZ, but I used the TOT method. I actually almost did it again, because in KitKat, my connection was very unstable, I did install the 35B baseband from XDABBEB, but that didn't fix the problem. I tried updating the firmware legitimately via LG Upgrade Assistant Utility (Verizon), but it kept giving an error everytime it got to 20%. I found no support online to get past this error, so I looked into stock ROMs and found XDABBEB (again) had built a flashable stock ROM for my phone, identical to what Verizon released last month, but with root access. I flashed TWRP 3.0 with Flashify, then flashed the ROM. The first time I flashed it, the phone showed that the phone service had stopped responding, a dialog box that only comes up once per cycle...super annoying. I managed to get back into Flashify and attempted installing the ROM again. I was actually prepared to do another TOT flash if it still had issues, but the second time wiping and flashing worked. My connection is solid, and I've had no errors (so far). It seems to run faster on Marshmallow than it did on Lollipop. It's pretty much the end result I was going for when I tried upgrading some 35 hours ago.
Update: Apparently, my baseband is fixed now. It did say Unknown before, even after flashing the 35B baseband from XDABBEB (initially anyways, reflashed after wipe just before flashing the ROM), but now it says "VS985-MPSS.DI.2.0.1.c1.13.4-00005-M8974AAAAANPZM-1"....so that's...good?
Click to expand...
Click to collapse
Awesome, well that's good that you eventually reached your goal. I can't say for sure why your connection was unstable on the Stock Kit Kat, but the 35B baseband is for 35B (5.1.1) Lollipop. The TOT method flashes back Stock Firmware, which is 10B (I believe 4.2.2) - KitKat so you would then need the Stock Modem IMG: (10B Modem File) but you are past that.. which is great. The Phone Service not responding is, I'm sure, a result of the incompatible 35B Modem mixing with 10B (4.2.2) Software Version. That's why flashing XDABBEB's Stock ROM fixed it (at least the second time around), because it includes all the stock IMGs, including the stock Baseband Version (10B).
But I'm so glad that you re-flashed and wiped again, because you have literally managed to return it to complete stock. Your baseband is official, and seems to me.. completely fixed!
Just confused with this:
It seems to run faster on Marshmallow than it did on Lollipop.
Click to expand...
Click to collapse
Are you running Marshmallow now? Or Kit Kat? I think I just lost you at some point haha.
But congrats on fully flipping your situation around! And in fact, because you fixed your Baseband issue, this thread is now completely answered! :good:
The TOT Method does wonders, doesn't it :victory:
Sorry, the stock ROM I used is http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's identical to what Verizon sent out last month except it is rooted, which I don't know why phone providers are so against letting their customers have full access to phones they either own or are leasing. I own this phone. It's paid in full. I want root access... Anyways, yes, it's Marshmallow.
Knux Kitsune said:
Sorry, the stock ROM I used is http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's identical to what Verizon sent out last month except it is rooted, which I don't know why phone providers are so against letting their customers have full access to phones they either own or are leasing. I own this phone. It's paid in full. I want root access... Anyways, yes, it's Marshmallow.
Click to expand...
Click to collapse
Ohhh, I see. I totally agree with you, it really makes no sense... the phone was built a certain way, it was meant to be used like that. Why the providers "nerf" them, I don't know. Even with the FM radio, they disable the receiver on the phones, I assume so that we are forced to stream instead, and they make more money. It's absolute sh**. But yeah, alright well that's cool, I might have to flash that myself actually, Marshmallow is lookin' really nice, as long as the battery life ain't too bad I'm gonna test it out myself!
Excuse me, first i´m sorry for my bad english language. I have same problem the unsupported baseband, but till now i just feel confused. I flash the Resurrection Remix Nougat on twrp and says unsupported baseband error. What should i do first? Flash the new baseband? If it yes, which baseband version is suitable for my device. Im using LG d855 and running android 6. Or i must unlock bootloader before flashing the new ROM? Thankyou, hope anyone will answer my stupid question.
I am using micromax q372 smartphone, had an android 5.0 stock ROM, and now i have installed resurrection remix 5.5.9, and my DEVICE OFFICIALY DOESN'T SUPPORT, and I garbed all of my luck and installed it, and now I have a fully working custom ROM on a unsupported device, the only problem I had was with the data connection, and I sorted it out, now everything is working, .............now I want to install resurrection remix 5.9.X , and my device doesn't is not on the support list, so ....can I do it , without any bugs? .......plz advice me