-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Help Restore backup after flashing Stock ROM?
- Thread starter Ily A
- Start date
Yeah I just flashed that, same issue. Since I'm able to flash recoveries fine, that must mean my bootloader is unlocked right? That can't be the issue?
Jfalls63
Android Expert
Is your current Android version LK3? If so that is older 4.1
4.4.2 OB3 is the newest. I think they expect you to be on the most current bootloader and baseband version
http://www.sammobile.com/firmwares/database/SGH-I747M/
4.4.2 OB3 is the newest. I think they expect you to be on the most current bootloader and baseband version
http://www.sammobile.com/firmwares/database/SGH-I747M/
Jfalls63
Android Expert
You need to be on the current firmware version you are on. I would delete the CM 12.1 zip file that you have and download it again.
Okay, I'll start this off by saying thank you for being so helpful and responding so quickly this entire time. I don't even know if I would have ever managed to get it done if it weren't for you.
That picture above was from me attempting to flash CM 10.1 which obviously didn't work cause it was expecting an older Android version. I had attempted to flash 12.1 several times earlier and I was getting an assertion error much like with 10.1, but instead of an old Android version, it was saying I had a d2vzw phone (which I don't) and I was trying to flash a d2att ROM (which I was). I read somewhere that removing the assertion from the update-script fixed that issue for a bunch of people, so I tried that and that just provided a less helpful error message. This was a couple hours ago, when I was using an old version of CWM.
I had that modified CM 12.1 zip on my phone the entire time, even when I upgraded to to the latest d2att version of TWRP. So after I redownloaded 12.1 and removed the old one, it actually flashed. I had never used TWRP before this, and tbh I wasn't even aware CWM wasn't being developed anymore. I knew both existed, but when I first started with CM back in 2012, CWM was the better choice, so I didn't even bother to consider TWRP would be a possible fix (also because I had flashed CM 12.1 last week over an older version of CM using CWM and it worked perfectly)
Anyways, I have CM 12.1 now, and I can finally close the 45 tabs I have open. Thanks again.
That picture above was from me attempting to flash CM 10.1 which obviously didn't work cause it was expecting an older Android version. I had attempted to flash 12.1 several times earlier and I was getting an assertion error much like with 10.1, but instead of an old Android version, it was saying I had a d2vzw phone (which I don't) and I was trying to flash a d2att ROM (which I was). I read somewhere that removing the assertion from the update-script fixed that issue for a bunch of people, so I tried that and that just provided a less helpful error message. This was a couple hours ago, when I was using an old version of CWM.
I had that modified CM 12.1 zip on my phone the entire time, even when I upgraded to to the latest d2att version of TWRP. So after I redownloaded 12.1 and removed the old one, it actually flashed. I had never used TWRP before this, and tbh I wasn't even aware CWM wasn't being developed anymore. I knew both existed, but when I first started with CM back in 2012, CWM was the better choice, so I didn't even bother to consider TWRP would be a possible fix (also because I had flashed CM 12.1 last week over an older version of CM using CWM and it worked perfectly)
Anyways, I have CM 12.1 now, and I can finally close the 45 tabs I have open. Thanks again.
Jfalls63
Android Expert
Pretty good guide for TWRP since it's different from CWM
http://www.androidtipsandhacks.com/root/twrp-the-complete-guide-to-using-recovery-on-android/
http://www.androidtipsandhacks.com/root/twrp-the-complete-guide-to-using-recovery-on-android/