Related
I currently have a brand new Canadian S4 with the MDJ firmware/baseband version.
Most of the roms are MDL based.
Do i have to change the base firmware/baseband to MDL before flashing and MDL rom ?
My goad is to install CleanRom wich is MDL based.
Thanks for the guidance.
Xetalx
Xetalx said:
I currently have a brand new Canadian S4 with the MDJ firmware/baseband version.
Most of the roms are MDL based.
Do i have to change the base firmware/baseband to MDL before flashing and MDL rom ?
My goad is to install CleanRom wich is MDL based.
Thanks for the guidance.
Xetalx
Click to expand...
Click to collapse
You can just flash the ROM. Just make a Nandroid backup first. Some ROM's come with a custom kernel and you may need to flash a Canadian kernel directly after flashing the ROM.
blyndfyre said:
You can just flash the ROM. Just make a Nandroid backup first. Some ROM's come with a custom kernel and you may need to flash a Canadian kernel directly after flashing the ROM.
Click to expand...
Click to collapse
I did get the original Kernel file for my cell provider. It is a TAR file with boot.img into it.
What is the easyest way to apply it after flashing the Rom in TWRP ?
Thanks
Xetalx
TARs are flashed with Odin or Mobile Odin.
Xetalx said:
I did get the original Kernel file for my cell provider. It is a TAR file with boot.img into it.
What is the easyest way to apply it after flashing the Rom in TWRP ?
Thanks
Xetalx
Click to expand...
Click to collapse
If you are flashing the STOCK firmware for your specific carrier it will include the STOCK kernel.
If you are using a custom ROM like Mint Jelly or something, I'd say flash Adam kernel after flashing the ROM. You won't want to flash a STOCK kernel with a custom ROM.
Did you end up updating to MDL?
I also have the MDJ kernel and I installed CleanRom, I now cannot get wifi and TWRP will not boot in recovery mode. I thought it would be easier just to update to MDL to get wifi but mobile Odin did not work.
Thank you
travisobvs said:
Did you end up updating to MDL?
I also have the MDJ kernel and I installed CleanRom, I now cannot get wifi and TWRP will not boot in recovery mode. I thought it would be easier just to update to MDL to get wifi but mobile Odin did not work.
Thank you
Click to expand...
Click to collapse
Regarding wifi on CleanROM, did you check post #2 here?
bo8 said:
Regarding wifi on CleanROM, did you check post #2 here?
Click to expand...
Click to collapse
No I did not,
Truthfully I am a pretty big Noob to all of this and was afraid of changing my kernel to MF3 from MDJ. I really didn't know how that would affect my phone / carrier situation here in Canada. The main problem was that I could not get the phone into recovery mode. Turns out I just needed to re-root the phone. So when I got the phone to actually go into recovery I jumped at the CM Rom. When I find a forum that helps me understand what updating my Kernel does to my phone I will try to update Kernel and go back to CleanRom. I kind of miss multiwindow.... maybe a little bit of Touchwiz...
Thanks for the reply!
EDIT : I also found this : http://www.scottsroms.com/downloads.php?do=file&id=421 which is a version of CleanROM made for the MDJ but it is dated further back which threw me for a loop too.
travisobvs said:
No I did not,
Truthfully I am a pretty big Noob to all of this and was afraid of changing my kernel to MF3 from MDJ. I really didn't know how that would affect my phone / carrier situation here in Canada. The main problem was that I could not get the phone into recovery mode. Turns out I just needed to re-root the phone. So when I got the phone to actually go into recovery I jumped at the CM Rom. When I find a forum that helps me understand what updating my Kernel does to my phone I will try to update Kernel and go back to CleanRom. I kind of miss multiwindow.... maybe a little bit of Touchwiz...
Thanks for the reply!
EDIT : I also found this : http://www.scottsroms.com/downloads.php?do=file&id=421 which is a version of CleanROM made for the MDJ but it is dated further back which threw me for a loop too.
Click to expand...
Click to collapse
No worries and you're very welcome! Don't sweat, I'm still on stock ROM because I'm hesitant to make the ROM dive. Don't know how or if installing MF3 kernel via custom ROM would affect the phone in terms of rooting or custom recovery either. I'd probably be sticking with MDJ build if possible.
You and me both on multiwindow! Helps a ton when it comes to referencing something while emailing/texting! I'd miss the TW camera as well ... maybe. haha
Which version of TWRP are you on? Version 2.6 has an often-experienced issue where it just hangs at the "teamwin" splash screen. Downgrading to 2.5.0.2 resolves that.
Any updates?
bo8 said:
No worries and you're very welcome! Don't sweat, I'm still on stock ROM because I'm hesitant to make the ROM dive. Don't know how or if installing MF3 kernel via custom ROM would affect the phone in terms of rooting or custom recovery either. I'd probably be sticking with MDJ build if possible.
You and me both on multiwindow! Helps a ton when it comes to referencing something while emailing/texting! I'd miss the TW camera as well ... maybe. haha
Which version of TWRP are you on? Version 2.6 has an often-experienced issue where it just hangs at the "teamwin" splash screen. Downgrading to 2.5.0.2 resolves that.
Click to expand...
Click to collapse
Hey guys,
I am also a 1337m Rogers S4 (MDJ) owner, also a noob as well. I managed to flash my phone with CM and had a pretty good AOSP experience and learned a little bit on the way. I can legitimately say that I miss a couple thing about stock / Touch wiz, mainly the multiwindow support and camera. Cyanogenmod is also acting up and drains battery pretty bad when I am roaming in the states.
What did you guys end up doing? Did you update your base-band to mdk and install CleanRom? Right now that looks like it's my goal but I truthfully have no idea how to do it.
Did you guys go back to stock after changing? Do I just find a stock ROM on the forum and use ODIN to bring it back?
Is switching roms as easy as choosing something in Goo manager or do you need to go into a recovery in recovery mode?
Thank you!
Hi guys,long time lurker here.
I have recently tried to update my old Nexus 2012 to Kitkat, and messed it up!:crying:
I can only get into TWRP now, and only get roms on there via a USB OTG cable.
Thing is, i've tried loads of roms and they all seem to fail. I've obviously messed up somewhere, anyone give me any poiinters?
Cheers.
EDIT
Think I'm sorted - seems i can't update to Kitkat, I tried a 4.2 rom, and all is good.
Note to self - do more research before 'updating':silly:
seymour71 said:
Hi guys,long time lurker here.
I have recently tried to update my old Nexus 2012 to Kitkat, and messed it up!:crying:
I can only get into TWRP now, and only get roms on there via a USB OTG cable.
Thing is, i've tried loads of roms and they all seem to fail. I've obviously messed up somewhere, anyone give me any poiinters?
Cheers.
Click to expand...
Click to collapse
If you took an OTA with stock firmware and TWRP, that's the issue. You can't boot into the bootloader to flash stock?
kcipopnevets said:
If you took an OTA with stock firmware and TWRP, that's the issue. You can't boot into the bootloader to flash stock?
Click to expand...
Click to collapse
Cheers dude, I think I'm sorted now, albeit at a 4.2 rom. What's the easiest way to update to 4.4?
seymour71 said:
Cheers dude, I think I'm sorted now, albeit at a 4.2 rom. What's the easiest way to update to 4.4?
Click to expand...
Click to collapse
For stock KitKat, use Nexus Root Toolkit and flash the stock binary, and enable USB debugging! Toolkit really takes over so it's kinda one click.
For a ROM? Update TWRP, CWM, or PhilZ to the latest version and pick a ROM that suits your fancy! Good luck on your journey!
kcipopnevets said:
For stock KitKat, use Nexus Root Toolkit and flash the stock binary, and enable USB debugging! Toolkit really takes over so it's kinda one click.
For a ROM? Update TWRP, CWM, or PhilZ to the latest version and pick a ROM that suits your fancy! Good luck on your journey!
Click to expand...
Click to collapse
Ah yes, I tried the toolkit when I thought I'd furbared by tablet, I'll enable debbinging & give it another go.
Cheers.
You probably need to update your bootloader to the latest.
You could flash stock 4.2.2 with fastboot.... And when you reboot, it will give you the kit kat ota. Which will update your bootloader and leave you on 4.4.2. Then you just need to flash recovery and root again.
kj2112 said:
You probably need to update your bootloader to the latest.
You could flash stock 4.2.2 with fastboot.... And when you reboot, it will give you the kit kat ota. Which will update your bootloader and leave you on 4.4.2. Then you just need to flash recovery and root again.
Click to expand...
Click to collapse
Hmmm, just tried this, everything seemed to go well, but it hasn't given the option of an ota update when I've rebooted. It's still showing as as CyanogenMod Version too?
seymour71 said:
Hmmm, just tried this, everything seemed to go well, but it hasn't given the option of an ota update when I've rebooted. It's still showing as as CyanogenMod Version too?
Click to expand...
Click to collapse
Hi, seymour71...
If you're running Googles official factory stock Android 4.2, then you can download the relevant OTA update(s) from here, directly to your Nexus 7, and flash in CWM or TWRP.
You can find out the specifics of the ROM build number your currently running by going to SETTINGS>>ABOUT TABLET>>BUILD NUMBER on your Nexus 7.
You may need to upgrade incrementally, that is to say, from 4.2 to 4.3 (and their successive point updates) right through to the latest version, Android 4.4.2 (Build number: KOT49H).
NOTE: OTA UPDATES ONLY WORK WITH OFFICIAL UNMODIFIED FACTORY STOCK... If you're running a Custom 4.2 based ROM, then flashing them will fail.
Good luck.
Rgrds,
Ged.
GedBlake said:
Hi, seymour71...
If you're running Googles official factory stock Android 4.2, then you can download the relevant OTA update(s) from here, directly to your Nexus 7, and flash in CWM or TWRP.
You can find out the specifics of the ROM build number your currently running by going to SETTINGS>>ABOUT TABLET>>BUILD NUMBER on your Nexus 7.
You may need to upgrade incrementally, that is to say, from 4.2 to 4.3 (and their successive point updates) right through to the latest version, Android 4.4.2 (Build number: KOT49H).
NOTE: OTA UPDATES ONLY WORK WITH OFFICIAL UNMODIFIED FACTORY STOCK... If you're running a Custom 4.2 based ROM, then flashing them will fail.
Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
Cheers dude. Just checked, the build number says: BeatMod CrystalClear v2.3
Android version is 4.2.2
I thought i'd just flashed it back to a 4.2 stock rom via the toolkit, but apparently not.
seymour71 said:
Cheers dude. Just checked, the build number says: BeatMod CrystalClear v2.3
Android version is 4.2.2
I thought i'd just flashed it back to a 4.2 stock rom via the toolkit, but apparently not.
Click to expand...
Click to collapse
"BeatMod CrystalClear v2.3"... Never heard of that one before. There are some pretty obscure ROMs out there. This one sounds like it has some sort of 'music' orientation.
Anyhow... it's a Custom ROM... and you wont be able to update it to 4.4.2 unless the developer has released a 4.4.2 version.
---------------------------------------------------------
Your best bet is to fastboot flash the official Google factory stock image for your specific Nexus 7(2012) model (WiFi only, or WiFi & 3G).
The Nexus 7(2012) factory image(s) can be found here...
https://developers.google.com/android/nexus/images#nakasi
Instructions on how to fastboot flash can be found here...
http://forum.xda-developers.com/showthread.php?t=1907796
Hope this helps.
Rgrds,
Ged.
Ah, it seems I didn't do it right properly first time.
I'm now on 4.2.2 with the build number JDQ39.
Would I be safe to flash a stock 4.4 rom using the toolkit now? It hasn't offered me an ota update - not yet, anyway.
Edit- It's doing it now, I think. Watch this space!
Hi I have an unrooted Samsung Galaxy S4 I9505 on Cyanogenmod M11, Was on UK VOD stock but moved to Cyanogenmod which is still on 4.4.4 KitKat but I'm a bit worried about future development of CGM. I read about tussles with other companies and big aspirations for M12 but the regular updates I've been enjoying have died out. not even a lollipop stable yet, I'm beginning to lose hope.
I know I shouldn't be so skeptical but I want to explore other roots (no pun intended).
Currently which rom would provide me with a stable lollipop with regular OTA updates for future proofing my phone?
Thanks v much
Alternatively I guess I could go back to stock to get lollipop but haven't done it in a while Im guessing I just flash a stock image via odin
Those tensions don't really affect Cyanogenmod, though I understand your concern. However, the biggest issue you're going to have is that most - if not all - custom ROMs are built using Cyanogenmod as a base. Realistically, the only alternative available I can think of without going to Touchwiz is Danvdh/Kryten's GPE ROM. Going back to Touchwiz is a dead end. Samsung has stated that Android 5.x is the end of the line for the S4, meaning there will be no Android M unless using a custom ROM.
Thanks very much for the excellent advice. I will give Danvdh/Kryten's GPE ROM a go and see how I go. I'm going to post the link to the ROM thread if anyone is following the same route as me: http://forum.xda-developers.com/showthread.php?t=2557353
EDIT: I'm going to try http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/rom-cyanogenmod-12-t2943934 first as its CM 12 lollipop which is what I was looking for really but will try GPE if i dont like that rom
Another question... sorry: i currently have CWM on my phone but the CM rom says to use TWRP with F2FS does cwm have this or do i need to remove CWM and install TWRP?
Trevsweb said:
Thanks very much for the excellent advice. I will give Danvdh/Kryten's GPE ROM a go and see how I go. I'm going to post the link to the ROM thread if anyone is following the same route as me: http://forum.xda-developers.com/showthread.php?t=2557353
EDIT: I'm going to try http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/rom-cyanogenmod-12-t2943934 first as its CM 12 lollipop which is what I was looking for really but will try GPE if i dont like that rom
Another question... sorry: i currently have CWM on my phone but the CM rom says to use TWRP with F2FS does cwm have this or do i need to remove CWM and install TWRP?
Click to expand...
Click to collapse
Don't use that version of CM. It's not what you want because it's not updated anymore.
Use this version:
http://forum.xda-developers.com/gal...lop/exclusive-antaresone-alucard24-s-t3066696
or the Official nightlies.
I used the older one but realised too late (
got stuck with no gapps and the bloody thing wouldnt boot into recovery cwm or twrp :/ never had that before. so having to do stock flash It's failed twice LOL
EDIT: got it stocked well thats something at least. anyway tomorrow I'll try again and get TWRP on there properly, it was weird because cyanogemod had installed CWM on there before i couldnt get rid of it :/ so i ended up with no recovery manager doh! Thanks for the link Lenny
Lennyz1988 said:
Don't use that version of CM. It's not what you want because it's not updated anymore.
Use this version:
http://forum.xda-developers.com/gal...lop/exclusive-antaresone-alucard24-s-t3066696
or the Official nightlies.
Click to expand...
Click to collapse
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
I have a US XT1687 on LineageOS (2017-09-19 build), and I would like to flash the latest stock firmware (which I believe is the April NPNS25.137-93-10 update), while also continuing to receive future OTA updates
The fastboot stock firmware thread was closed.
I found these files https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ but I don't see the 93-10 update.
Can I flash the 93-4 update from that site via fastboot and then get the 93-10 update via OTA?
Thanks!
I believe it depends on what bootloader version you were on before. If you were on 93-4 or earlier, then theoretically you should be fine. If you were on the 93-10 version of the bootloader and attempted to flash to the 93-4 stock rom, and then take an OTA from there, you are very likely going to hard-brick your device.
There are a lot of active threads about flashing back to stock and losing IMEI and enhanced LTE, so I wouldn't risk it. Out of curiosity why would you want to flash back to stock Nougat? IMO the camera is worse and you're rolling back to an older OS.
dunderball said:
I believe it depends on what bootloader version you were on before. If you were on 93-4 or earlier, then theoretically you should be fine. If you were on the 93-10 version of the bootloader and attempted to flash to the 93-4 stock rom, and then take an OTA from there, you are very likely going to hard-brick your device.
There are a lot of active threads about flashing back to stock and losing IMEI and enhanced LTE, so I wouldn't risk it. Out of curiosity why would you want to flash back to stock Nougat? IMO the camera is worse and you're rolling back to an older OS.
Click to expand...
Click to collapse
I'm actually still on Nougat. The last time I flashed a new ROM was back in September (the LineageOS build I'm using is from 2017-09-19). So my bootloader is likely whatever the latest one was around that time.
From what I read, it seemed like people were losing their IMEI and VoLTE after flashing 8.1 custom ROMs, which I haven't done, so I figured I was safe. Maybe I'm misunderstanding?
Yousie642 said:
I'm actually still on Nougat. The last time I flashed a new ROM was back in September (the LineageOS build I'm using is from 2017-09-19). So my bootloader is likely whatever the latest one was around that time.
From what I read, it seemed like people were losing their IMEI and VoLTE after flashing 8.1 custom ROMs, which I haven't done, so I figured I was safe. Maybe I'm misunderstanding?
Click to expand...
Click to collapse
Ah I wasn't aware that you were on a nougat version of LOS. I would still back up all partitions just in case.
dunderball said:
Ah I wasn't aware that you were on a nougat version of LOS. I would still back up all partitions just in case.
Click to expand...
Click to collapse
Is that different from doing a NAND backup in TWRP?
Yousie642 said:
Is that different from doing a NAND backup in TWRP?
Click to expand...
Click to collapse
Nope it's the same.
Yousie642 said:
I have a US XT1687 on LineageOS (2017-09-19 build), and I would like to flash the latest stock firmware (which I believe is the April NPNS25.137-93-10 update), while also continuing to receive future OTA updates
The fastboot stock firmware thread was closed.
I found these files https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ but I don't see the 93-10 update.
Can I flash the 93-4 update from that site via fastboot and then get the 93-10 update via OTA?
Thanks!
Click to expand...
Click to collapse
Here's a mirror of the 93-10 firmware, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud but not everyone was able to download it from there.
If you changed to a custom rom in September 2017 you should have been on August security patch which is the firmware NPNS25.137-33-11.
But you should be good to go with 93-10.
As written above make sure to have a full nandroid, especially of EFS.
Sent from my Moto G5 Plus using XDA Labs
dunderball said:
Nope it's the same.
Click to expand...
Click to collapse
Wolfcity said:
Here's a mirror of the 93-10 firmware, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud but not everyone was able to download it from there.
If you changed to a custom rom in September 2017 you should have been on August security patch which is the firmware NPNS25.137-33-11.
But you should be good to go with 93-10.
As written above make sure to have a full nandroid, especially of EFS.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Thanks dudes! I actually found my old adb folder and saw I had the files for NPN25.137-83 extracted there, so I'm pretty sure that's what I'm on. Seems like it still won't be an issue though.
What I am worried about now is losing VoLTE if I ever decide to go back to a custom ROM. Though, from what I understand, as long as I have an EFS backup, I can fix it. Is that right?
Yep you should be fine. I didn't have issues when going from stock to custom. Still -- I'd try out an Oreo rom before jumping back to stock.
dunderball said:
Yep you should be fine. I didn't have issues when going from stock to custom. Still -- I'd try out an Oreo rom before jumping back to stock.
Click to expand...
Click to collapse
Y'know, it didn't actually occur to me, and this may be a silly question, but now I'm wondering if there's actually any need to run a stock firmware update before going to newer custom ROMs? The reason I ask is because this was a thing with my Nexus 5x. Newer LineageOS builds sometimes needed a bootloader and radio update.