Develop Bugs

[Q] Restore android 4.1.2 from 4.4.2

Not sure if this is the right place to post this as it is my first on this forum, I have Samsung galaxy s3 I747 d2att. Current rom...ROM][4.1.2][Sept 29] Hyperdrive RLS16...bootloader.... I747UCDLK3. Before I flash any of the 4.4.2 roms I need to know if I can restore to my current rom. I have read some threads that are adamant that once you flash to 4.4 you CANNOTgo back to a previous backup of 4.1.2...others are just as adamant that you CAN restore from a cwm or other backup if you desire to go back. I understand if you have a mjb bootloader, or have 4.3 ota update you are locked into android 4.3 or 4.4. I have neither of those. I use CWM mostly but also have & use TWRP, & have current backups of both, Can I flash a cw11 nightly rom, Quantum v3 rc4, or [ROM][4.4.2][Unofficial] Liquid Smooth v3.0 [12/14/13] [D2att] (which has no bootloader), or other 4.4.2 roms & still be able to restore from backup? I believe a lot of the comments about not being able to go back had to do with using the newest bootloader or the knox problem, but I am not sure what to think, & am trying to avoid flashing to 4.4.2 & having to stay there. Thanks

cybrgeek 45 said:
Not sure if this is the right place to post this as it is my first on this forum, I have Samsung galaxy s3 I747 d2att. Current rom...ROM][4.1.2][Sept 29] Hyperdrive RLS16...bootloader.... I747UCDLK3. Before I flash any of the 4.4.2 roms I need to know if I can restore to my current rom. I have read some threads that are adamant that once you flash to 4.4 you CANNOTgo back to a previous backup of 4.1.2...others are just as adamant that you CAN restore from a cwm or other backup if you desire to go back. I understand if you have a mjb bootloader, or have 4.3 ota update you are locked into android 4.3 or 4.4. I have neither of those. I use CWM mostly but also have & use TWRP, & have current backups of both, Can I flash a cw11 nightly rom, Quantum v3 rc4, or [ROM][4.4.2][Unofficial] Liquid Smooth v3.0 [12/14/13] [D2att] (which has no bootloader), or other 4.4.2 roms & still be able to restore from backup? I believe a lot of the comments about not being able to go back had to do with using the newest bootloader or the knox problem, but I am not sure what to think, & am trying to avoid flashing to 4.4.2 & having to stay there. Thanks
Click to expand...
Click to collapse
You can flash anything that has no bootloader attached to it. You can do 4.4.2 without updating the bootloader. My wife has gone from 4.1.2 Jedi ROM, to 4.4.2 Nightlies, and back to 4.3 Jedi ROM with no issues. She stayed on the 4.1.2 bootloader MF1 believe. My phone on the other hand did update to the 4.3 stock rom and bootloader (MK5). Even after this update I was still able to go to CM11, as Cyanogenmod does not contain a bootloader that will conflict. Afterwards you can even come back down to other ROMS as long as any of these roms do not contain bootloaders in them. Post # 3 may be able to help[ you with a few of your questions as to what you can and can not flash. http://forum.xda-developers.com/showthread.php?t=2558311. Don't worry there is always a way back from 4.4.2.

BCSC said:
You can flash anything that has no bootloader attached to it. You can do 4.4.2 without updating the bootloader. My wife has gone from 4.1.2 Jedi ROM, to 4.4.2 Nightlies, and back to 4.3 Jedi ROM with no issues. She stayed on the 4.1.2 bootloader MF1 believe. My phone on the other hand did update to the 4.3 stock rom and bootloader (MK5). Even after this update I was still able to go to CM11, as Cyanogenmod does not contain a bootloader that will conflict. Afterwards you can even come back down to other ROMS as long as any of these roms do not contain bootloaders in them. Post # 3 may be able to help[ you with a few of your questions as to what you can and can not flash. http://forum.xda-developers.com/showthread.php?t=2558311. Don't worry there is always a way back from 4.4.2.
Click to expand...
Click to collapse
Thanks for the quick response & the link. I have been searching & agonizing over this for 3-4 days. This is just the answer I needed!

[Q]Need clarification for rooted rogers note 2, android 4.4

Hello, I recently just updated my Rogers SGH-i317M to 4.3, which then downloaded a system update which put it at 4.4. I was running Jedi X20, which is based on 4.1.2, when I first tried updating, I flashed the "4.3param_tz" file in odin, and was left with an error screen saying I need to recover using Kies, so I downloaded the official release, flashed via odin, and thats how I got to where I am now. I want to try the "Ditto Note 3" rom, "Sky Note Air 4.3", "Mean Bean" and "Beanstalk". My main question is, can I just start flashing these roms like I was before on 4.1.2, or do I need to use the specific kernel listed on their page? Before you needed a specific kernel to run a touchwiz rom or an aosp rom, so is it still the same? Or can I use my stock 4.4 kernel and try both aosp and tw roms now? If so could you point out the kernels I would need? And educate me on anything else I should know about before flashing 4.3 and 4.4 roms, (I'm not worried about warranty), this would be greatly appreciated. Thanks for your time in reading this and helping me out, much appreciated!!

Regardless of where u are, I'd Odin to Rogers stock KK 4.4.2. Then Odin Twrp recovery, boot into twrp recovery and flash SU v.1.99. Finally choose your rom and flash away. This way you are on the lastest KK 4.4.2 Bootloader and KK Modem/Baseband.

just_visiting said:
Regardless of where u are, I'd Odin to Rogers stock KK 4.4.2. Then Odin Twrp recovery, boot into twrp recovery and flash SU v.1.99. Finally choose your rom and flash away. This way you are on the lastest KK 4.4.2 Bootloader and KK Modem/Baseband.
Click to expand...
Click to collapse
I did all that except flash SU 1.99, so I tried flashing SKynote Air and it didnt work, upon restarting my phone it said no os is available. So I tried restoring from the backup I made of the official 4.4.2 Samsung rom in twrp, didn't work. Tried Odin, didn't work. Then I tried flashing the Skynote rom again and it worked. So I'm afraid of flashing any other roms now.

[Q] CM 10.2 (d2att) install fails with "Update Binary".

I am trying to flash GS3 (Canadian Rogers unlocked) i747m with cm10.2 d2att from SD through Philz Touch, but my install fails half thru "Installation aborted, please update binary"
I made 2 backups to SD card, so I easily recovered back, but trying to understand what has happened, first time doing it, and I am not sure why. Please help.
Model: SGH-I747M
Android: 4.4.2
Baseband: I747MVLUFNF2
Kernel: 3.4.0-1784548
Build: KOT49H.I747MVLUFNF2

Any particular reason you want cm10.2? Since you are on a KK bootloader and modem, I would go with a cm11 install for the d2lte.
Is your recovery up to date?

audit13 said:
Any particular reason you want cm10.2? Since you are on a KK bootloader and modem, I would go with a cm11 install for the d2lte.
Is your recovery up to date?
Click to expand...
Click to collapse
Only reason was that 10.2 is stable release and I wasn't sure if cm11 is compatible with my bootloader.
Philz Touch 6 Recovery , I believe was the last build for d2lte I found.
Philz Touch 6.48.4 ClockworkMod v6.0.5.0

Not sure why you're getting that error. CM10.2 is basically JB while CM11 is KK.
I suggest trying CM11.

audit13 said:
Not sure why you're getting that error. CM10.2 is basically JB while CM11 is KK.
I suggest trying CM11.
Click to expand...
Click to collapse
Thanks,
I tried cm11 and install was flawless.

How to flash roms not based off 4.1.2 JB?

Hi, I'm having issues flashing roms which aren't based off of 4.1.2 firmware. I am rooted on 4.1.2 JB and have flashed a few of the 4.1.2 roms on my tmobile s3 t999, when I attempt anything else it fails with "error 7" for example cm10 and 11 or 4.3/4.4. Please Help? Thanks.

1. Make sure you're on latest version of recovery.
2. You may need to ODIN to a newer version/bootloader.

ShernDog said:
1. Make sure you're on latest version of recovery.
2. You may need to ODIN to a newer version/bootloader.
Click to expand...
Click to collapse
I tried flashing over the bootloader update found here. http://forum.xda-developers.com/showthread.php?t=2282603
and am receiving a "status 7" error once again. I restored a backup which contained no mods, downloaded rootkeeper and booted into cwm tried flashing the updated zip, it returned a status 7 error. I'm not sure how to proceed. I am currently using 4.1.2 axis with trinity kernel. I cant seem to flash anything whatsoever aside from roms based off 4.1.2. Can someone help me step-by-step?
thanks

Update recovery

thanks guys. Success!!!

[Q] Which Firmware W/ Fresh SlimKat 9 Stable Install

Background: I attempted to update from SlimKat 7.0 stable to 9.0 stable and discovered my apn's were missing and when I try to add them manually it fails to save. I have also found others with this same issue but none have an easy fix. I'm on UCDLK3 firmware, after restoring to previous state using nandroid backup apn's are present. If I try to flash any ROM (even other than Slim) my apn's are missing, even a dirty flash of 7.0 over 7.0. I know I can fix this by flashing stock UCDLK3 and root/twrp/flash slim 9 and everything will likely work fine. I plan to do just that but want to make sure I'm doing things as smart and clean as possible. There is a lot of info out there and I'm finding it hard to sift through old stuff and find the current state of things.
Question: Is there an actual advantage if I upgrade the firmware from UCDLK3 to UCUEMJB while still planning to use SlimKat 9 Stable with BMS kernel and TWRP recovery? Are there any disadvantages? Either way what is the shortest path to get back to stock (either LK3 or MJB) and flash SlimKat?
Thanks

Your APN may not be sticking because your modem and bootloader may be too outdated.
Some of the latest CM11 and AOSP ROMs require a KK bootloader and modem.

And then there are some roms that require at least a 4.3 bootloader and modem, either the MJ2 (leaked) or MJB (official) bootlaoder/modem combos. I have seen mention of these working in some OPs and in the body of other threads. In some of the later TW ROMs you may have to use a custom kernel like kt747 or iBuddler's. I don't know if any kernel other than the stock in SlimKat and AOSP ROMs would be needed with the MJ2/MJB firmware and modem.
I don't know of any advantages other than some of the ROMs require firmware newer than DLK3 to properly boot, receive data, or have a working wifi. As far as disadvantages, KNOX was introduced with the MJB firmware and stock ROMs, once going to MJB or newer firmware you can not make firmware downgrades without a very real risk of hardbricking your phone. Also you will need to insure your baseband and modem versions match. If they do not you risk hardbricking of another variety.
I had not yet realized that the newer AOSP and CM11 required you to go all of the way to NE4, thank Audit.

Just wanted to close the loop on this thread and say thanks for the assistance!
I now have my phone working properly on SlimKat 9; it really was just the firmware not being compatible with newer ROMs as many have suggested. Here is the sequence I followed to do it but really it probably only needed a twrp flash of the mjb firmware and the ROM install:
1. Used odin to restore to stock LK3 (only because I had messed with things so much and wanted a clean slate)
2. Used odin to install TWRP 2.7.1.0 recovery
3. Rooted with SuperSU 2.40 using TWRP
4. Flashed combined MJB modem & bootloader using TWRP
5. Flashed SlimKat 9 using TWRP
6. Flashed Slim GApps using TWRP
7. Rooted with SuperSU 2.40 using TWRP (Lost root after flashing ROM)

thanks for posting fix. am sure it will help others. audit13 and dawgdoc , thank you for continued help with the awesome Slll. :good:
"all i can really do , is stay out of my own way and let the will of heaven be done"

jeff.leonard said:
Just wanted to close the loop on this thread and say thanks for the assistance!
I now have my phone working properly on SlimKat 9; it really was just the firmware not being compatible with newer ROMs as many have suggested. Here is the sequence I followed to do it but really it probably only needed a twrp flash of the mjb firmware and the ROM install:
1. Used odin to restore to stock LK3 (only because I had messed with things so much and wanted a clean slate)
2. Used odin to install TWRP 2.7.1.0 recovery
3. Rooted with SuperSU 2.40 using TWRP
4. Flashed combined MJB modem & bootloader using TWRP
5. Flashed SlimKat 9 using TWRP
6. Flashed Slim GApps using TWRP
7. Rooted with SuperSU 2.40 using TWRP (Lost root after flashing ROM)
Click to expand...
Click to collapse
When you restored to LK3, what Firmware version were you coming from? I'm looking to go to LK3 from the NJ1. However there seems to be cautionary red flags all over the place due to bootloader changes that were made in 4.3.

The OP was already on LK3 with a custom ROM.
Since you are on NJ1, you cannot downgrade the bootloader.