I recently flashed the temasek and official CM11 roms, but the baseband has been unknown since.
So I had flash back to the original rom that I was using, my QUESTION is that I like cm11 alot, so how can i fix this problem?
Which Note model? -- N9005 or N9005 variant? -
T/w8 ?
Which recovery do you use?
radicalisto said:
Which Note model? -- N9005 or N9005 variant? -
T/w8 ?
Which recovery do you use?
Click to expand...
Click to collapse
It is actually N9006 but temasek's v45 for n9005 and earlier worked fine, I am using CWM rec.
Until recently, temasek's v46 and 47, the baseband becomes unknown
Last time a user had that issue, he fixed it by flashing stock via odin and then CM but he was using a n9005 so I am not sure if that will work for you as well...However no harm in trying.
Sent From My SM-N9005 To All You Wonder Nobodies!!
Khizar said:
Last time a user had that issue, he fixed it by flashing stock via odin and then CM but he was using a n9005 so I am not sure if that will work for you as well...However no harm in trying.
Sent From My SM-N9005 To All You Wonder Nobodies!!
Click to expand...
Click to collapse
I'm sorry but I speak poor English. What is a Stock? I've tried flashing kernel and baseband but it did not work.
When I use Temasek's v45, it shows that my baseband is ML1, but when I use further version, it becomes unknown.
Stock is your original Samsung ROM
Sent from my CM11 Kitkat powered N9005
radicalisto said:
Stock is your original Samsung ROM
Sent from my CM11 Kitkat powered N9005
Click to expand...
Click to collapse
ok i see, i tought it was sth like baseband or kernel or sth else.
I just flashed a n9006 rom made by chinese romers to get my note mp4 into a note3, or i could just use temasek's v45.
I just wanna use the latest cm11 rom but it seems that it's not quite possible for now, so i'll just stick to my original rom...
radicalisto said:
Stock is your original Samsung ROM
Sent from my CM11 Kitkat powered N9005
Click to expand...
Click to collapse
are there kernels and basebands that don't match, i mean they just don't work when put together?
I actually got to a similar problem, after some cyanogenmod update I suddenly got no cellular service at all signal strength stuck on -120db and its stuck on searching for service, flashing older versions, wipes, all did nothing
qlum said:
I actually got to a similar problem, after some cyanogenmod update I suddenly got no cellular service at all signal strength stuck on -120db and its stuck on searching for service, flashing older versions, wipes, all did nothing
Click to expand...
Click to collapse
We have probably same issue
Aditmac1 said:
We have probably same issue
Click to expand...
Click to collapse
I am going to try flashing back to stock tonight, I will report back if it works.
qlum said:
I am going to try flashing back to stock tonight, I will report back if it works.
Click to expand...
Click to collapse
it worked for me though
It also worked for me although sadly I could not use my backup again after flashing back to cyanogenemod so its time to start downloading. At least my phone is fully functional now, even if I lost a bit of data.
I had the same issue move than once, i would lose imei number etc.
Found out that it wasn't prompting for pin unlock on boot.
Since removing this I've had no problems
Yea it also wasn't prompting for ping with mine.
Though starting again fresh does work, I am currently again on the latest nightlies. however if this happens again I will probably wait for a stable release because having to reinstall everything is not really desirable.
qlum said:
Yea it also wasn't prompting for ping with mine.
Though starting again fresh does work, I am currently again on the latest nightlies. however if this happens again I will probably wait for a stable release because having to reinstall everything is not really desirable.
Click to expand...
Click to collapse
it is rather annoying to reinstall everything,even with kies
I didn't even use kies nor any other tool like that.
Related
Ok, so previously with my S4, if we flashed a I9505 ROM onto a I337or I337M S4, all we had to do was flash our device models custom or stock kernel and the wifi and everything that was borked was then fixed. This doesn't seem to be the case here.
And now I can't figure out for the life of me how to get back wifi after flashing a 9005 ROM on my N900!
I'm sure it's something super simple, and I;ve searched for the solution, but clearly I'm looking in the wrong place.
Any assistance would be met with a "Thanks" and some karma points
Did you flash a custom firmware or a stock one?
Sent from my SM-N9005 using Tapatalk
RavenY2K3 said:
Did you flash a custom firmware or a stock one?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Custom. More specifically Fox Hound
TheSmokingAndroid said:
Custom. More specifically Fox Hound
Click to expand...
Click to collapse
Ok well that blows out what I thought you'd done it.
Have you tried wiping after flashing the correct ROM? The "incorrect ROM" didn't include any modern files didn't (not that I'm sure CWM will flash them on this phone however)
Strange question, but is your camera still working? Recording etc... also, in device settings, does it list the correct IMEI number?
Sent from my SM-N9005 using Tapatalk
Yup, camera works with stock kernel that the rom came with, imei is fine.
Just can't figure out which files to flash to get wifi and other radios working
Yup, camera works with stock kernel that the rom came with, imei is fine.
Just can't figure out which files to flash to get wifi and other radios working
Did you try a factory reset? After backing up of course...
Might work....
As title, looking for the 4.3 touchwiz based rom's that work with the old bootloader.
Almost all custom roms you can flash from recovery won't update your bootloader. I recommend omega.
Read OP of any rom and you will sure notice that the bootloader will remain untouched after flashing.
dkreventon said:
Almost all custom roms you can flash from recovery won't update your bootloader. I recommend omega.
Read OP of any rom and you will sure notice that the bootloader will remain untouched after flashing.
Click to expand...
Click to collapse
There will be no issues like lack of sound, wifi etc?
Been using GE roms since the new bootloader was introduced but I have read posts from users having problems flashing new firmware with old bootloader, or is that just for the official roms?
As long as you have the latest modem (MJ5) there won't be any issues.
http://forum.xda-developers.com/showpost.php?p=48972299&postcount=18311 - Check the installation instructions.
dkreventon said:
As long as you have the latest modem (MJ5) there won't be any issues.
http://forum.xda-developers.com/showpost.php?p=48972299&postcount=18311 - Check the installation instructions.
Click to expand...
Click to collapse
I'm already using that modem so might just give it a try.
Thanks for the help.
Be sure to have the latest philz touch and you're good to go!
Flashed Omega V19, all working.
Definitely not as smooth as the GE roms but it 's not bad, also it's nice to have the Samsung Camera back again.
Also give echoe rom ago, I'm on old bootloader and mk9 modem, working much better than 4.2.2 stock
Sent from my GT-I9505 using xda app-developers app
ranger4740 said:
Also give echoe rom ago, I'm on old bootloader and mk9 modem, working much better than 4.2.2 stock
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Thanks, might give that a try as Omega just started rebooting randomly..
Will try another kernel, if that doesn't fix it then ill try echoe.
All custom roms since 4.3 gave me random reboots once every couple of days.
I'm currently running omega v19 and the uptime is 48h.
Well I got Omega stable with KT kernel, but found the lag a bit annoying so tried echoe rom anyway.
Sadly the lag is much the same, I guess it's a feature of touchwiz and nothing can be done about it.
Why havent Samsung fixed this? it's almost the same as the original roms that phone shipped with.
With the recent files being dumped for note 5. Would it be possible to have it ported over to the s5 with some changes, without having to wait til the official release?
I do not think it's possible,as we do not have sources for 6.0 kernel on klte :| But still,hope someone can do some kind of workaround.
just to try the new marshmallow test cm 13 really to home
Wolf80 said:
I do not think it's possible,as we do not have sources for 6.0 kernel on klte :| But still,hope someone can do some kind of workaround.
Click to expand...
Click to collapse
Yeah that's what I was hoping.
superacc75 said:
just to try the new marshmallow test cm 13 really to home
Click to expand...
Click to collapse
I've tried it. It never boots on my g900t. No cm roms seem to work on my s5. Am I doing something wrong? Lol
It might be possible, as there are few unofficial CM13 (Android 6.0) builds already available for our Galaxy S5. Let's just wait and hope someone out there with kind heart and adequate time develop one for our phone.
Vineen said:
It might be possible, as there are few unofficial CM13 (Android 6.0) builds already available for our Galaxy S5. Let's just wait and hope someone out there with kind heart and adequate time develop one for our phone.
Click to expand...
Click to collapse
Yeah i cant get cm 13 to work. :/ or else i would use that.
daddymemoru said:
Yeah i cant get cm 13 to work. :/ or else i would use that.
Click to expand...
Click to collapse
The unofficial CM13 build by @albinoman887 can be actually used as a daily driver.
Vineen said:
The unofficial CM13 build by @albinoman887 can be actually used as a daily driver.
Click to expand...
Click to collapse
It always seems to get stuck in a bootloop for me. Help?
daddymemoru said:
It always seems to get stuck in a bootloop for me. Help?
Click to expand...
Click to collapse
Which varient you have? Which recovery? Which gapps? How are you downloading?
Zehlek said:
Which varient you have? Which recovery? Which gapps? How are you downloading?
Click to expand...
Click to collapse
I have the g900t (T-Mobile) using TWRP. Open gapps 6.0 (where you can choose your own). And I download off the XDA pages with my phone.
I should also note that only touchwiz Roms seem to work. Any cm ROM always gets stuck at bootloop, I can sometimes getting it to optimizing apps by switching kernel, but then it reboots over and over without starting.
daddymemoru said:
I have the g900t (T-Mobile) using TWRP. Open gapps 6.0 (where you can choose your own). And I download off the XDA pages with my phone.
I should also note that only touchwiz Roms seem to work. Any cm ROM always gets stuck at bootloop, I can sometimes getting it to optimizing apps by switching kernel, but then it reboots over and over without starting.
Click to expand...
Click to collapse
I use these gapps
https://www.androidfilehost.com/?fid=24269982086988288
What I do is
-Download ROM and gapps with chrome on my phone
-reboot into twrp
-wipe system, data, cache, dalvik
-flash ROM(klte unified)
-flash gapps
- boot
I have 900w8 variant but that shouldn't matter
Sent from my SM-G900W8 using Tapatalk
Zehlek said:
I use these gapps
https://www.androidfilehost.com/?fid=24269982086988288
What I do is
-Download ROM and gapps with chrome on my phone
-reboot into twrp
-wipe system, data, cache, dalvik
-flash ROM(klte unified)
-flash gapps
- boot
I have 900w8 variant but that shouldn't matter
Sent from my SM-G900W8 using Tapatalk
Click to expand...
Click to collapse
Yeah just get stuck in a bootloop.
daddymemoru said:
It always seems to get stuck in a bootloop for me. Help?
Click to expand...
Click to collapse
Make sure you've performed a full wipe before flashing it and if you're planning on using Google apps then make sure to flash them before booting into CM13 or else you'll get stuck with lots of FCs.
Vineen said:
Make sure you've performed a full wipe before flashing it and if you're planning on using Google apps then make sure to flash them before booting into CM13 or else you'll get stuck with lots of FCs.
Click to expand...
Click to collapse
Yeah I've tried that. CM Roms don't ever boot for me for some reason.
daddymemoru said:
Yeah I've tried that. CM Roms don't ever boot for me for some reason.
Click to expand...
Click to collapse
Have you tried downgrading to KitKat then repeating the process again?
Sent from my SM-G900F using XDA Forums
Vineen said:
Have you tried downgrading to KitKat then repeating the process again?
Sent from my SM-G900F using XDA Forums
Click to expand...
Click to collapse
I thought you couldn't do that with the latest 5.1.1 update. If you can I'd like some steps so I can try. because knowing me I'd get lost somewhere. >.<
daddymemoru said:
I thought you couldn't do that with the latest 5.1.1 update. If you can I'd like some steps so I can try. because knowing me I'd get lost somewhere. >.<
Click to expand...
Click to collapse
Is your bootloader unlocked? Because as far as I know, there are variants of the Galaxy S5 which have their bootloaders unlocked, making them impossible to downgrade or else making their device bootloop.
As for the steps, you only have to download the KitKat firmware (I recommend ANE2 - easiest to root) from sammobile.com then flash it via Odin.
Make sure you have Samsung Mobile Drivers installed if you are working on a Windows environment. Afterwards, root your Galaxy S5 by downloading towelroot from towelroot.com.
Once done, download SuperSU on Play Store. Flash custom recovery using Rashr. Make sure Reactivation Lock is disabled before flashing anything custom or else it will cause problems.
When you have custom recovery successfully installed, try flashing CyanogenMod again.
Sent from my SM-G900F using XDA Forums
Vineen said:
Is your bootloader unlocked? Because as far as I know, there are variants of the Galaxy S5 which have their bootloaders unlocked, making them impossible to downgrade or else making their device bootloop.
As for the steps, you only have to download the KitKat firmware (I recommend ANE2 - easiest to root) from sammobile.com then flash it via Odin.
Make sure you have Samsung Mobile Drivers installed if you are working on a Windows environment. Afterwards, root your Galaxy S5 by downloading towelroot from towelroot.com.
Once done, download SuperSU on Play Store. Flash custom recovery using Rashr. Make sure Reactivation Lock is disabled before flashing anything custom or else it will cause problems.
When you have custom recovery successfully installed, try flashing CyanogenMod again.
Sent from my SM-G900F using XDA Forums
Click to expand...
Click to collapse
OK I'll try that. I have T-Mobile g900t. I'm pretty sure its unlocked. Lol I'd be the happiest person ever if it works. I used to have blisspop, but now the ROM doesn't work.
daddymemoru said:
OK I'll try that. I have T-Mobile g900t. I'm pretty sure its unlocked. Lol I'd be the happiest person ever if it works. I used to have blisspop, but now the ROM doesn't work.
Click to expand...
Click to collapse
Report back if everything goes fine. TouchWiz Lollipop caused me a lot of problems in modding mainly because it's harder to mod it unlike KitKat which is pretty straight forward.
By reverting to KitKat, I was able to use XtreStoLite which stopped working on me for some time. Now I'm on Android Marshmallow 6.0.1 (CyanogenMod 13 unofficial by @albinoman887) and I'm satisfied than ever.
Sent from my SM-G900F using XDA Forums
I have a GT-i9505 that I've been running the stock Jellybean Touchwiz 4.2.2 ROM on since forever (I9505XXUAMDD). I recently discovered compatibility issues with some updated apps and decided to give the latest Touchwiz a spin. Since my phone is rooted i couldn't get the update via OTA so I downloaded the latest Touchwiz ROM (I9505XXUHOL2) and flashed it manually. It went well but I didn't really like it and I didn't have the time to set everything up again so I restored my original setup using a nandroid backup but now things are all wonky. I can't mount my SD card and wifi won't turn on. I suspect this is because the kernel is still the one from the 5.0.1 flash while the ROM is back to the 4.2.2 one. Under the about device menu the android version shows 4.2.2 and the build number is the original I9505XXUAMDD but the baseband version shows I9505XXUHOL2 and the kernel version shows 3.4.0-431985. In addition when booting up the phone it shows the "SEAndroid...kernel" message in the top left corner; not sure what this is.
Is there a way to remedy this or am I SOL and forced to use a later version of Android? Thanks in advance!
Edit: So further research suggests it's actually the Baseband version that is causing the problem so flashing the correct modem should fix it. Could someone please show me which modem is correct for I9505XXUAMDD? Also, will this fix the kernel message I keep getting? Thanks!
You can't downgrade from lollipop that easily
There's threads in general relating to downgrading
Could be a mismatch between the phone bootloader and baseband. What bootloader version and baseband is on the phone? If they match, it could just be that the bootloader and modem are too new for the rom.
DSA said:
You can't downgrade from lollipop that easily
There's threads in general relating to downgrading
Click to expand...
Click to collapse
Yeah, I realize that now. I put too much faith in the nandroid restore. I had tried out the JFLTE-GPE ROM once before and a nandroid restore reverted the device without issue so I just assumed it would do the same in this situation. I will look into the downgrade process.
audit13 said:
Could be a mismatch between the phone bootloader and baseband. What bootloader version and baseband is on the phone? If they match, it could just be that the bootloader and modem are too new for the rom.
Click to expand...
Click to collapse
I was under the impression that a nandroid restore would flash the bootloader as well but my faith in nandroid backups isn't what it used to be
Guess I'll have to look for the appropriate bootloader and modem for the ROM.
You can install the Samsung Phone Info app from the Play store to confirm your bootloader and modem.
audit13 said:
You can install the Samsung Phone Info app from the Play store to confirm your bootloader and modem.
Click to expand...
Click to collapse
Wifi is out so I don't have access to the play store
I used the terminal emulator to check the bootloader version and it's indeed still on I9505XXUHOL2. I've read somewhere that once a newer version of the knox bootloader has been installed, attempting to flash back to the 4.2.2 bootloader will brick the phone. Is this true?
Thanks again!
I don't know about the 9505 but you can't downgrade on the s3, i337, and note 2.
Personally, I would flash back to stock to make sure everything still works.
audit13 said:
I don't know about the 9505 but you can't downgrade on the s3, i337, and note 2.
Personally, I would flash back to stock to make sure everything still works.
Click to expand...
Click to collapse
Will do. I'll pull up the I9505XXUAMDD from sammobile and give that flash when I get home this evening. Thanks again!
So I flashed to stock I9505XXUAMDD but the wifi and sd card issue remains and the bootloader still shows up as I9505XXUHOL2. Not sure how to proceed.
I'm starting to get the feeling that 4.2.2 is a lost cause...I guess downgrade on GT-i9505 is not possible.
Edit: Baseband version is now I9505XXUAMDD and wifi is still not working.
Update: Flashed to I9505XXUHOF2 and everything seems to be all peachy keen for now. Will update again once I restore all my apps and data.
aznpos531 said:
So I flashed to stock I9505XXUAMDD but the wifi and sd card issue remains and the bootloader still shows up as I9505XXUHOL2. Not sure how to proceed.
I'm starting to get the feeling that 4.2.2 is a lost cause...I guess downgrade on GT-i9505 is not possible.
Edit: Baseband version is now I9505XXUAMDD and wifi is still not working.
Update: Flashed to I9505XXUHOF2 and everything seems to be all peachy keen for now. Will update again once I restore all my apps and data.
Click to expand...
Click to collapse
No it's not. It's not possible because you cannot downgrade the bootloader.
Perhaps you can still go back with 4.2.2. custom rom but in my opinion it's really not worth it. It's not worth to stay on an outdated version with all the security vulnerabilities. I would recommend anyone to use CM because then you can run the latest software on your phone.
Lennyz1988 said:
No it's not. It's not possible because you cannot downgrade the bootloader.
Perhaps you can still go back with 4.2.2. custom rom but in my opinion it's really not worth it. It's not worth to stay on an outdated version with all the security vulnerabilities. I would recommend anyone to use CM because then you can run the latest software on your phone.
Click to expand...
Click to collapse
Thanks for confirming and thanks for your input :good:
I really did enjoy the Jellybean experience on the S4; going to Jellybean from ICS felt like an upgrade. I feel like that was the best match for the phone and it just went downhill from there (as far as the S4 is concerned). I suppose it's time to move on.
Update: All apps and data fully restored and it seems stable save for some small quirks. Not liking Lollipop though.
So I had DarkLord N5 on my N9005 before, which was awesome, but it had performance issues (especially when gaming). Then i downgraded to Stock KitKat using Odin and after boot up It showed No Signal, and everything was freezing and force closing. I somehow went to settings and found that i also have issues with IMEI and Baseband version, it was all unknown. The worst part is i did not backup my EFS. Any help guys please :crying:
I also have no audio playback
Im no pro here, but as i found in my research it is hard to downgrade from lolipop to kitkat as in 5.0 new architecture has been presented which they called art. I think. So it gives lots of incompatibilities. I tried the same as you but i ended up going stock lolipop for a while.
Yesterday i flashed Ressurrection remix 6.0.1 Marshmallow based off Slim roms and CM and i admit this is so far best rom i have tested. (Unless you need all fancy spen features)
I'd try to stick to anything that is 5.1 or above since great battery life.
Sorry for not much info, but i couldn't get past your post unanswered.
oxoconstantineoxo said:
Im no pro here, but as i found in my research it is hard to downgrade from lolipop to kitkat as in 5.0 new architecture has been presented which they called art. I think. So it gives lots of incompatibilities. I tried the same as you but i ended up going stock lolipop for a while.
Yesterday i flashed Ressurrection remix 6.0.1 Marshmallow based off Slim roms and CM and i admit this is so far best rom i have tested. (Unless you need all fancy spen features)
I'd try to stick to anything that is 5.1 or above since great battery life.
Sorry for not much info, but i couldn't get past your post unanswered.
Click to expand...
Click to collapse
I had many experiences with downgrading from new version to old version with my S3 and my Note, but never had this issue. Something is causing this...
founded a old backup of CM11.. Flashed CWM and restored to CM. Works flawlessly, but still no sound and those stuff
Honix5962 said:
I had many experiences with downgrading from new version to old version with my S3 and my Note, but never had this issue. Something is causing this...
Click to expand...
Click to collapse
So i had problems with my either s2 or note 4.
But afaik if u have updated your bootloader there may be no way to get back. And lack of IMEI on reverted KitKat isn't anything new. I bet going simply to anything art. Based will do.
People here are arguing on same issues as yours. Just don't listen to these "flash with odin" guys.. This doesn't work. Even if u flash the stock one.
http://forum.xda-developers.com/gal...o-downgrade-lollipop-to-kitkat-t2990262/page2
Hope you will dig up something.
You could try this. It worked for me.
http://forum.xda-developers.com/showthread.php?t=2507403
Have you tried flashing to the latest stock rom for the phone using Odin?
audit13 said:
Have you tried flashing to the latest stock rom for the phone using Odin?
Click to expand...
Click to collapse
Nope, I downloaded the KitKat firmware from Sammobile, and I'm downloading the Lollipop one now.
deejhay14 said:
You could try this. It worked for me.
http://forum.xda-developers.com/showthread.php?t=2507403
Click to expand...
Click to collapse
I tried it, but still no use :c
I would not try any other ROMs before trying to flash the latest stock rom from sammobile.com. Hopefully, this will resolve the baseband and imei issue. Sometimes, the missing or wrong imei is caused by a mismatch between the bootloader and modem firmware.
audit13 said:
I would not try any other ROMs before trying to flash the latest stock rom from sammobile.com. Hopefully, this will resolve the baseband and imei issue. Sometimes, the missing or wrong imei is caused by a mismatch between the bootloader and modem firmware.
Click to expand...
Click to collapse
I hope so.
I have seen this sort of problem on the Samsung s3 and note 3 phones.
audit13 said:
I have seen this sort of problem on the Samsung s3 and note 3 phones.
Click to expand...
Click to collapse
I did downgrading from 5.0 (CM12) to Stock 4.4 KitKat in my S3, but never had issues like this.
Downgrading from a cm rom to a stock rom via Odin can be fine because installing a cm rom does NOT alter the phone's bootloader or modem. Trying to downgrade from stock 4.4.2 to stock 4.3 with Odin on an s3 cannot be done.
audit13 said:
Downgrading from a cm rom to a stock rom via Odin can be fine because installing a cm rom does alter the phone's bootloader or modem. Trying to downgrade from stock 4.4.2 to stock 4.3 with Odin on an s3 cannot be done.
Click to expand...
Click to collapse
Oh, never knew about this, thanks for the info
Sorry, I meant to say that installing a cm rom DOES NOT change the bootloader or modem. When you flash back to stock via Odin, you are simply writing over the existing modem and bootloader with the same bootloader and modem if you are flashing the same stock rom that was on the phone before installing cm.
I flashed between KitKat and LP official just fine.
audit13 said:
Have you tried flashing to the latest stock rom for the phone using Odin?
Click to expand...
Click to collapse
Never mind, It works. Thanks for the help.
Which method worked? Thanks.
Use gsii repair