Good Day.
Got my z1c a couple weeks ago and am loving it. Managed to root it. I have yet to pull the trigger on unlocking the bootloader. I have seen lots of AOKP and CM based roms but are there any Sony Based Modified Roms to keep the Camera processing intact? I am not the biggest fan of CM although I am sure its improved over the years but the camera and battery issues are of no interest to me that I keep reading in the majority of the roms posted. So can you please point me to some Sony Based Modified Roms (if they even exist)? Aslo, do I have to unlock the bootloader to put on another Sony based ROM? Lastly, I do have to unlock the bootloader if I want TWRP or CWM correct? TIA!
You can find some custom Sony Roms in original dev section. Usually you don't need unlocked bootloader for Sony roms.
You also don't need unlocked bootloader for recovery, see for example dualrecovery http://forum.xda-developers.com/showthread.php?t=2261606
You could try this if you're up to a bit of experimenting: http://forum.xda-developers.com/showthread.php?p=54330224
I've been using RomAur 9.1 for quite a while now without any issues, but with a locked bootloader you'd lose recovery if XZDualRecovery still isn't working. Somebody would have to try if a current version works, I'm using encryption which makes it a bit complicated for me otherwise I'd try it myself.
Thank you both for your help. I installed recovery without issue. Now to find a nice fluid ROM. It is difficult coming from Google Edition Roms!!!!
Hi,
I know this information is probably available somewhere, but I have spent hours of reading, and still having some trouble getting my head around things. So I will try to be clear here as to what my issues are.
Firstly... I have Samsung Galaxy S-III, SGH-i747M, with virgin mobile canada. It started with android 4.1.2. I wanted to unlock it, and there was a way to do it with 4.1.1 (http://forum.xda-developers.com/showthread.php?t=2176719), so I used odin, with firmwares (found at SamMobile.com I think) to flash a 4.1.1 ROM, did the unlock procedure, and then used odin to flash stock firmware for 4.1.2 again. Seems to have all worked out ok.
Anyway, I want to try some custom roms, like cyanogenmod, as they are purported to improve battery life, speed, clearing off bloatware, giving me more control, etc.
However, I really want to maintain the ability to go back to how it is now, if I don't like the custom roms. (or if I need warranty help, though there's not much of that left).
The main thing that's concerning me is that while I was playing with this phone before, I read in a number of places that if I had updated to Android 4.3 or 4.4.2 when those had become available from my carrier, I would not have been able to downgrade to 4.1.1 (which I needed to be able to do to use the built-in unlock method). This is because of Knox, which would be installed, and gets "tripped." So now I'm scared: if I did that upgrade, I wouldn't have been able to revert; so now, if I flash a CGM ROM, will I also be unable to revert?
I think there are a few pieces of android to sort out in my mind... If I'm not mistaken, there's bootloader, there's recovery, and there's the ROM. Flashing a ROM with Odin apparently would restore recovery and the ROM? But not the bootloader (that's where knox is? though I still don't understand, if an upgrade can modify the bootloader and put knox there, where it wasn't before, shouldn't there be a way to put a pre-knox version back there?)
Oh, there's also EFS, which some say should be backed up before doing anything (though you need to root first, which in my mind counts as doing something before backing it up).
Anyway, please let me know if you can help clarify these issues, thanks!!
There is a lot to cover to address all that you bring up.
Regarding EFS, there are a number of ways to back it up. Use several. This thread is an excellent place to start for more info and several ways to make the backup. I was rooted, so I used A2 and B. I believe you can use A1 without being rooted, probably B as well. Long after that post was written wanam came out with two backup apps available in the PlayStore. One was specifically for EFS, but I do not think it is still supported. The other is a more comprehensive app, both require root.
As a rule, bootloaders and modems are not installed with custom ROMs. If you are flashing a stock ROM from these forums that is installed from within a custom recovery it probably does not install a bootloader and modem either, but read the relevant thread to be certain. Full stock ROMs flashed from with Odin, or Heimdall, almost certainly install a bootloader and modem.
Prior to 4.3 there was an ability to downgrade bootloaders and modems, nor were they required to match - be at the same version. Once you upgrade to the official 4.3 bootloader you can no longer downgrade it. Once you have upgraded to 4.4.x the bootloader and modem versions must always match. If they are mismatched you risk soft bricking your phone at a minimum. For the i747 there was an unofficial 4.3 release; ROM, bootloader, and modem. I do not recall seeing mention of an unofficial release for the i747M, so I will not go into the exceptions on the above the unofficial bootloader/modem introduced.
For TouchWiz ROMs, custom or stock, the bootloader (and modem) version should match or be more current than the ROM Android version. (One of the unofficial 4.3 release exceptions applies here, I make use of it.)
For CyanogenMod, CM based ROMs, AOSP ROMs, and their derivatives the bootloader and modem version can lag behind Android version of the ROM. With your 4.1.2 bootloader and modem you could run the earlier releases of 4.4.x CM and AOSP ROMs. Later in the 4.4.x development, around Oct or Nov 2014 IIRC, I began reading reports of needing to be on 4.3 or later, there were a few said the 4.1.2 firmware still worked for them. For the 5.x.x LP releases of CM and AOSP most report that they must be on a 4.4.x bootloader and modem.
Knox is in the ROM, not the bootloader and modem. It was introduced with the official 4.3 releases. It is not present in CM/AOSP nor most of the custom TW ROMs. It will be present in stock ROMs from official sources or sites like sammobile. Many of the stock ROM images/dumps have Knox disabled, especially those from enewman17, but read to make sure what you are getting.
I don't feel qualified to discuss tripping the Knox counter, I am still on the unofficial 4.3 bootloader, which has not kept me from running 4.4.x ROMs. I am not the only Luddite, but I feel we will all be updating bootloaders and modems due to the Stage Fright bug. I am long out of warranty so there is no loss.
ABOVE ALL, read thoroughly before taking any action. Keep in mind that I am on the i747 and not the i747M as you are, I am not be correct on all comments for your device. @audit13 should be able to clear any gaffs I have made.
@dawgdoc is correct about everything said.
It is not Knox that prevents downgrading from 4.3 to an earlier version, it is the code in the bootloader itself.
Ok, starting to feel a bit more comfortable with the whole system and relationships, thanks!
audit13 said:
@dawgdoc is correct about everything said.
It is not Knox that prevents downgrading from 4.3 to an earlier version, it is the code in the bootloader itself.
Click to expand...
Click to collapse
Thanks for verifying that. There could have easily been small, but very important, differences in the devices that had slipped my mind since I don't have the i747M.
This is the way xda should be. Good questions from a concerned user & great answers from @dawgdoc. Nice job guys!
canodroid15 said:
This is the way xda should be. Good questions from a concerned user & great answers from @dawgdoc. Nice job guys!
Click to expand...
Click to collapse
I would like to extend similar praise and thanks to @mrrocketdog and @audit13
more uncertainty
Hi,
I'm a lot more experienced now, having rooted (I flashed root66_BMC_I747MVLDMF1 by MrRobinson, since CF-autoroot just made the phone show "booting recovery" then blank screen indefinitely), I backed up EFS by a couple methods, flashed TWRP, did a nandroid backup, and flashed a couple versions of CM. Still a few things I want to clarify though.
Unsurprisingly, after flashing the final CM 11 release, data did not work, as I'm still on the 4.1.2 (MF1) bootloader/modem. In general, I see a lot of posts simply saying "update the modem." From what you've said though, that will create problems, unless I update the bootloader as well, correct? Just feels like the phrase "update the modem" is said so casually, without also mentioning the bootloader, and the inability to go back.
(an older CM 11 worked with data just fine)
(a big issue is that S3 is over 3 years old, so there are over 3 years of posts, so there's a lot of conflicting information, likely due to different versions, new discoveries, etc. )
I'm not quite sure myself what I'm trying to ask, I guess it's something along the lines of "am I just being silly by not updating?" There are a lot of "Never update to 4.3 (or above) because of knox!" comments. But also in general, it seems the only real issue with knox is that warranty bit, otherwise it doesn't have too big an impact on our lives? Seems the consensus is that we can still root, install custom roms, and everything else. (Do you know if this remains true with latest bootloaders and modems (OB3 for i747M). There are also "My battery life became way worse after the upgrade" or "more FCs" or other issues, which is a significant concern if my phone which currently comfortably lasts a day starts to not last a day after updating. Though it's likely a small percent noting that, while the quieter majority are fine. Meanwhile, by not updating, we may be missing out on features and security improvements (and maybe actually improved performance). What do you guys think? (I know dawgdoc was sticking to an unofficial 4.3 rather than updating, so it's not an obvious choice).
As for updating, I think somewhere one of you suggested the better (or at least safer) way is to use odin to flash stock ROM, then do the OTA updates, or, directly flash the latest stock ROM, rather than trying to flash modems and bootloaders directly?
Once I have a 4.3 or 4.4.2 bootloader/modem, I can delete any old TWRP nandroid backups from when I had 4.1.2 since restoring them would cause a brick? Same for EFS backup (which backed up EFS, Modem, Modemst1, and Modemst2 partitions)
Thanks again!
I almost wish I'd just taken the blue pill at the start of all this
For XDA members that are new to rooting, flashing, etc., I always recommend the safest route which is to flash back to a completely stock ROM and just upgrade to the latest bootloader and modem via OTA updates. There's always a risk of something going wrong when flashing anything, be it a custom ROM, recovery, or OTA update.
If the phone still had warranty, I recommend not flashing any non-Samsung software until the warranty has expired. Once expired, flash away
Knox should not interfere with root if supersu is flashed from a custom recovery, regardless of the bootloader. I have used supersu to root the latest s3, s4, Note2, and Note3 ROMs without a problem.
Restoring old nandroid backups should not cause a brick as TWRP does not change the modem or bootloader.
sacrawfo said:
....Still a few things I want to clarify though.
Unsurprisingly, after flashing the final CM 11 release, data did not work, as I'm still on the 4.1.2 (MF1) bootloader/modem.....
(an older CM 11 worked with data just fine)
I'm not quite sure myself what I'm trying to ask, I guess it's something along the lines of "am I just being silly by not updating?" ....(I know dawgdoc was sticking to an unofficial 4.3 rather than updating, so it's not an obvious choice).
Once I have a 4.3 or 4.4.2 bootloader/modem, I can delete any old TWRP nandroid backups from when I had 4.1.2 since restoring them would cause a brick? Same for EFS backup (which backed up EFS, Modem, Modemst1, and Modemst2 partitions)
Click to expand...
Click to collapse
I think the change date for CM11 requiring the newer bootloaders, at least NE4, is Nov 2014. Releases prior to that date would run fine on older bootloaders.
I have since updated to NE4 in order to run ROMs patched with the StageFright fixes, specifically CM11 20150831. Knox isn't installed on this ROM or even the newer custom TouchWiz based ROMs. I am not concerned about Warranty Bit being triggered. My device is long past being covered by any warranty and I have no intentions of using Knox features on this phone in a corporate environment.
Keep the EFS backups, those are from partitions not changed by flashing roms; stock or otherwise.
Finally went through the OTA updates, surprised how long it took but all done, at OB3.
Ok makes sense, restoring an old Nandroid would effectively result in a 4.1.2 OS with a 4.4.2 bootloader/modem, which != brick.
Still surprised that modem updates do not effect the "modem" partition that EFS backup saved.
Thanks,
Restoring a nandroid backup should not brick the phone brick the phone as twrp does not restore the modem or bootloader.
sacrawfo said:
...
Still surprised that modem updates do not effect the "modem" partition that EFS backup saved.
Thanks,
Click to expand...
Click to collapse
There are quite a few partitions not affected by flashing, not only the EFS partitions. IIRC there are secondary modem partitions, more than two extra bootloader partitions, etc.
Hello,
Picked up my OP3 on Monday (Contract with o2 in the UK) and itching to flash a new ROM. Just has a few questions.
Does the all in one toolkit still work? Comfortable with adb and fast boot but toolkit is obviously easier and quicker.
Currently running latest firmware is there any precautions to take when flashing ROMs etc? On previous devices it's been a simple boot into TWRP/CWM, wipe, flash ROM/gapps and happy days. Are all ROMs compatible?
Noticed OnePlus don't consider unlocking a bootloader and flashing etc worthy of voiding a warranty- does this mean if anything did happen at some point and I was running custom ROMs that o2 will still repair it or do they not follow OP's after care? Whilst im on this topic; Can you relock the bootloader with ease if anything was to happen?
Finally which 7.X ROM is the most stable with good battery life and plenty of features? Personal favourite has always been PACman but haven't had a chance to scroll through the current ROMs for this device yet. On my G3 many custom ROMs which weren't based on stock had terrible camera quality, is this common on the OP3 too?
Thanks,
Curtis
1. Yes the toolkit should still work
2. Flashing roms is the same as all other devices
3. If the problem was not caused because of the custom rom the they will repair it for you i guess.
4. And as far as battery life is concerned it is determined more by the kernel than the rom. I would recommend exkernel and official cm14.1
Thank for your reply!
Another question haha, can I just unlock bootloader, load up TWRP, boot into recovery, wipe, install any ROM and I'm golden? Saw a few threads say firmware X.X.X aren't compatible and you need to jump to X.X.X for it to work as well as some fingerprint problems occurring if not using a certain build?
Just wondering if the above is all old stuff that has been ironed out haha
Thanks
If your flashing cm14.1 based ROMs then you would need to flash correct firmware which would be in installation instructions or help threads but oos stock based ROMs will have everything included
Hi guys, I've been reading a lot of different threads, but have gotten myself confused. Its been a long time since I done flashing of software, and things are completely changed since then.
Anyway,I currently have the z5 premium which was purchased in o2, however I have now moved to ee and would like the WiFi calling feature. My handset hasn't been rooted or nor can the bootloader be unlocked. Can I still download stock ee firmware and install it without any problems.
I find most branded firmware to be buggy in some way.
there is a tutorial for backing up your TA partition ( the bit that keeps your DRM keys)
https://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
and a tutorial for unlocking your bootloader, and compiling a patched Stock Kernel. from there, you will be able to install any of our great Custom roms.
https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
If you decide instead to keep your phone locked. you should still be able to flash a stock rom using the FTF and the flash tool. you should still backup all your data, photo's documents etc before doing anything at all with your phone.
and always try to start any new flash completely clean. and build up from there, instead of trying to retain your data, or restoring your apps.
If you want more help with backing up and rooting / unlocking your bootloader just ask. but post the exact model version of your device. as the z5p has 4 different models.
Thanks for the reply Patrick, I got all sorted. Unfortunately the bootloader can't be unlocked on my handset, so can't use custom ROMS. However, I was able to use Flashtool and XperiFirm to download EE's branded firmware, and now I have the WiFi calling feature. Thanks for your help.
Got myself a Redmi Note 5 Global version and want to update MIUI and possibly try a custom ROM. Just came here to make sure i'm not falling for any common mistakes before i do anything especially after reading a lot of folks that have bricked these devices due to Anti Roll-back so thats the last thing i want to do. The device came boxed with MIUI 9.5.6.0(OEIMIFA) and i've just ignored the update notification up to now so i presume i've avoided ARB and i would like to keep it that way.
So just to confirm are these the correct steps.
1. Unlock the bootloader
2. Flash a custom recovery (TWRP or the equivalent)
3. Update MIUI / Flash custom rom package without ARB and flash through TWRP
Is there anything i'm missing or anything i need to specifically avoid other than ARB?
drkdeath5000 said:
Got myself a Redmi Note 5 Global version and want to update MIUI and possibly try a custom ROM. Just came here to make sure i'm not falling for any common mistakes before i do anything especially after reading a lot of folks that have bricked these devices due to Anti Roll-back so thats the last thing i want to do. The device came boxed with MIUI 9.5.6.0(OEIMIFA) and i've just ignored the update notification up to now so i presume i've avoided ARB and i would like to keep it that way.
So just to confirm are these the correct steps.
1. Unlock the bootloader
2. Flash a custom recovery (TWRP or the equivalent)
3. Update MIUI / Flash custom rom package without ARB and flash through TWRP
Is there anything i'm missing or anything i need to specifically avoid other than ARB?
Click to expand...
Click to collapse
Just don't update your firmware (or update it with a ARB-less firmware), that's what will trigger ARB. Most of the customs rom don't contain firmware, only LOS advises you to flash a specific version, but MIUI roms do.
So you either steer away from those and flash fw-less roms, or you just delete the firmware-files folder from the rom and flash it without them.
This is my advice, before flashing anything, open the zip and check for the firmware folder. If it has it, delete it (unless is specified by the dev to flash that along the rom, in that case, just avoid it, there's a plethora of custom roms to choose from).
Ok thanks so i'll just stay clear of any roms containing the firmware folder for now. I do like LOS but if theres any risk associated i'll just give it a miss for now.
I also assume its easy to recover from a bad flash following the no firmware folder rule since theres no real risk associated with flashing just a ROM(no firmware)?
Finally, what about kernels and bootloader updates is there anything specific i need to watch out for there? I only ask because my previous device included a sneaky OTA update which locked the bootloader and i'd obviously like to avoid anything like that here.
Sorry for all the questions i'm just a bit behind on the flashing front, my previous device was a Motorola Razr HD and flashing seems to have changed quite a bit since then.
drkdeath5000 said:
Ok thanks so i'll just stay clear of any roms containing the firmware folder for now. I do like LOS but if theres any risk associated i'll just give it a miss for now.
I also assume its easy to recover from a bad flash following the no firmware folder rule since theres no real risk associated with flashing just a ROM(no firmware)?
Finally, what about kernels and bootloader updates is there anything specific i need to watch out for there? I only ask because my previous device included a sneaky OTA update which locked the bootloader and i'd obviously like to avoid anything like that here.
Sorry for all the questions i'm just a bit behind on the flashing front, my previous device was a Motorola Razr HD and flashing seems to have changed quite a bit since then.
Click to expand...
Click to collapse
No problems, happy to help if I can.
And yes, no risk if you don't flash firmware. Worst case scenario, you'll have to reflash a miui rom with MiFlash, which means losing your data, but imo it's better than bricking the device.
As for kernels and bootloader, you're good to go. Nothing will relock your bootloader (except flashing with MiFlash and selecting that specific option) and a kernel in the worst case will just give you a bootloop. Use backups. ?
And as far as LOS goes, you can flash it without the specified firmware (even tho I'm pretty sure it's an ARB3 firmware) but I guess there might be some small issues.
Good luck with unlocking the bootloader, that thing takes from 720 to 1440 hours, just got my rn5p in a week now i have to wait a month before rooting...