Related
Hi,
I'm having problems with space and the general speed of my Xperia Arc S so the time has come to finally upgrade from Sony's version of Android 2.3 in hope that it will improve things.
I've kind of avoided this so far as I don't really know the best way to back-up things.
I want to back up to my computer - not to the internet.
I am guessing that for the applications that I would like to back up I would need to back up both their APK files and whatever their setting files are. I guess there are also some system settings to back up (but then these are less important).
A problem I have always had is space on the phone - it has very little storage space and although I try and move everything to the SD card, a lot of it doesn't seem to be able to be moved.
Things like simply the Google Play services take up loads of space! I don't even really have that much on there - mainly just whatsapp.
The phone is stock although I have checked in the service menu and it says that I can unlock the bootloader. Part of the reason I didn't upgrade to Sony's version of Android 4 was because I heard that it locks the bootloader and I didn't know if this was bad.
What is the bootloader unlock for? Is it for loading custom roms? As i thought you could do this even if it was locked? Or is it for rooting?
So yer, I guess I am looking for recommendations for a CFW to suit my needs. Priorities are that it works and i'm guessing the latest android version possible would be best as this will help with performance etc. Or is that a misnomer as newer android releases are generally geared for phones with higher specs? I've heard that some CFWs have problems with wifi etc so i'd like to avoid those as I certainly need that.
Overall there seem to be so many even on this forum that I don't really know which would be a best fit for my needs or this phone.
I also have an original San Francisco (zte blade) to update but will save that 'till I've done this one.
Hopefully I can get an understanding as to how all this CFW / Rooting / whatever business works and the best / latest way to do things, as as with everything, it all rapidly changes and you can find yourself looking out lots of outdated and now incorrect or superseeded information.
All a bit overwhelming really, which is why i've put it off so long!
Thanks for your time and help!
1. Q : For backup on ICS 4.0.4, right?
A : Unlock bootloader first -> root -> flash cwm - now u can backup everything from ur phone.
2. Q : Little storage, right?
A : After backup, reboot system.
Partition ur sdcard -> install link2sd. (google it for how to)
Link what do u want to link (google it for how to)
3. Q : Unlockbootloader, right?
A : It's for using custom kernel (google it for how to)
There's too many tutorial from all your question.
Read it again and again :good:
Abigail said:
1. Q : For backup on ICS 4.0.4, right?
A : Unlock bootloader first -> root -> flash cwm - now u can backup everything from ur phone.
2. Q : Little storage, right?
A : After backup, reboot system.
Partition ur sdcard -> install link2sd. (google it for how to)
Link what do u want to link (google it for how to)
3. Q : Unlockbootloader, right?
A : It's for using custom kernel (google it for how to)
There's too many tutorial from all your question.
Read it again and again :good:
Click to expand...
Click to collapse
I have android 2.3 - is this a problem?
I thought that the Sony ICS 4.0 update made it so you could not unlock your bootloader?
Hmm if you unlock your bootloader, it will also root the phone, correct?
But it seems that using the Sony tool will wipe my phone developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
So i saw there is the S1tool but then people said that it does not work with the Arc S.
Is this still the case? What is the reason? is it impossible?
So, you say that in order to back up my applications and things, i need to unlock my bootloader. The official way seems to wipe my phone though - so then i can't back up :S
Hmm, see, i am confused about the order i should do things. Also i've heard that if you use the Sony tool then you cannot use OTA updates which seems like it could be problematic? Mind you i guess CFW cannot use OTA either - so how do you update? You must check for updates on your PC and reflash your phone regularly? Or are there ways for Stock android CFW to support OTA updates?
So, does the Sony ICS update stop you unlocking the bootloader?
I guess there are 2 options. Update using that and then install helium OR root and then use titanium backup.
Not sure which to try.
Thanks!
1. Unlock bootloader is only affected by the phone manufacture date, check the battery compartment and see if the date is before 12W11. Any date after this means the phone can't be unlocked.
2. Software does not affect the unlocking of bootloader, like I mentioned earlier check the battery compartment.
3. Unlocking your bootloader does not mean you have rooted your phone. It just means you can flash custom kernels onto your phone.
4. It's not that S1tool doesn't work, if I told you the entire process of doing it you wouldn't want to do it either.
5. Sony last stopped the update at 4.0.4, no need to concern yourself with future updates.
6. If you use CFW, refer to the thread for instructions on how to install updates.
7. Like I mentioned, ICS update does not affect bootloader unlock, only the manufacture date does. Furthermore, if you update from stock to a CFW, you will not be able to restore your data from the old software. You will have no choice but to start with a clean slate.
I am on Sonys 2.3, build 4.0.2.A.0.62 and i read that i cannot root this version.
I can't use backup software as i can't root to use titanium and helium doesn't support 2.3.
Sony back also apparently doesn't support my phone.
Basically, my apps are outdated due to me not having enough space to update them.
I think that updating to Sony's ICS update might enable me to use these programs and root so that i can backup, then unlock the bootloader and use cfw. (i checked and my s# is older than 12W11 so that's fine).
However, i am worried that if i try to update to Sony's ICS update that i will either lose my applications or the data that is stored with them (whatsapp history, game saves, app config etc etc) - particularly as they are not up to date.
Is this the case? Is there anything i can do?
Thanks
oneNight1 said:
I am on Sonys 2.3, build 4.0.2.A.0.62 and i read that i cannot root this version.
Click to expand...
Click to collapse
Take a look at the tool namend one click root (this thread: http://forum.xda-developers.com/showthread.php?t=2219781), your build should be root-able, just read carefully and decide if you wanna try...
I used this tool on stock sony ics 4.0.4 build and it worked nicely, haven't tried it on stock sony gb 2.3 build though.
Good luck! :good:
BadGround said:
Take a look at the tool namend one click root (this thread: http://forum.xda-developers.com/showthread.php?t=2219781), your build should be root-able, just read carefully and decide if you wanna try...
I used this tool on stock sony ics 4.0.4 build and it worked nicely, haven't tried it on stock sony gb 2.3 build though.
Good luck! :good:
Click to expand...
Click to collapse
Thanks for the tip! It worked!
If you do it twice it relocks your phone. Took some google translate to find out what the chinese was saying hehe.
I'm now on stock 4.0.3 (4.1.A.0.562).
Doesn't seem a great deal better than 2.3, i guess i need to find out what a good lightweight CFW is really. Firefox for android constantly crashes so i tried naked browser and that does too. Wish there was a good selective script blocker for mobile browsers - that would help a lot. Noscript for firefox would be a possibility but the problem is it crashes a lot even with javascript disabled.
So yer not sure where the problems are coming from, maybe due to the low RAM in this phone. That's why i was thinking a lightweight CFW might help matters but not sure if it's best to go with a 5.1 one that breaks 720p recording and has issues with things like turning off GPS.
Or it might be better to go with the latest type that doesn't break anything. I'm guessing that is a 4.0.4 CFW? Or maybe 4.4? I know stock only goes up to 4.0.4 but i think i read something about being able to get CFW based on stock so HDMI, FM radio, 720p recording etc etc won't be broken?
Thanks anyway!
oneNight1 said:
Or it might be better to go with the latest type that doesn't break anything. I'm guessing that is a 4.0.4 CFW? Or maybe 4.4? I know stock only goes up to 4.0.4 but i think i read something about being able to get CFW based on stock so HDMI, FM radio, 720p recording etc etc won't be broken?
Click to expand...
Click to collapse
Well, I haven't tried 5.1 so far, only following the 5.1-threads to see how it's going on.
HDMI is only working up to 4.0.4 roms, FM radio is working in 4.1 roms too, and you'll get 720p recording also in 4.4.4 roms. If you want all things working your phone is able to you will have to use roms based on stock GB or ICS. Therefore I'm using a stock based ICS rom most of the time (T-Rom).
By T-Rom for Arc S, i assume that you mean this? http://forum.xda-developers.com/showthread.php?t=1746508
Or if not then this port of it? http://forum.xda-developers.com/showthread.php?t=2239187
Sounds like something worth trying to see if it helps!
Thanks!
oneNight1 said:
By T-Rom for Arc S, i assume that you mean this? http://forum.xda-developers.com/showthread.php?t=1746508
Or if not then this port of it? http://forum.xda-developers.com/showthread.php?t=2239187
Sounds like something worth trying to see if it helps!
Thanks!
Click to expand...
Click to collapse
For Arc S the first link is the matching one. I think it's the most recently updated ICS rom for our device :good:
Hi,
After doing some reading on here I am a little unsure on the best way to back up my HTC One M9 (GSM) stock recovery/system. My software number is 3.50.710.1 (Android 6.0) and it came from Optus (Australia). I cannot seem to find an RUU file for this firmware anywhere online; only earlier versions are available. My understanding of this is that I need an RUU file for my specific firmware as a fail-safe in case I mess something up and need to return to stock?
My questions are:
1) Can I get my phone back to the current complete stock firmware and be able to receive future OTA updates without turning s-off and without copying anything from my phone before I flash TWRP and a custom ROM?
2) If not is there anyway that I can back up my phone it its current stock state that will allow me to go back to this state if I want to go back to my stock Optus firmware or to install OTA updates? (Including the stock radio/recovery)
3) Reading this post as well as others leads me to believe that I may stop my mobile radio working by flashing a custom ROM (especially as the linked post has the exact same firmware as me). How can I avoid this, or fix it if it happens to everyone?
I am ideally looking for a custom ROM which improves over the stock firmware. My priority is maximum battery life, with customisation and HTC 10 system UI/apps a secondary focus. Any recommendations would be great, as well as tweaks and kernels which help give the maximum battery life.
Cheers!
You can't backup your firmware (and that includes your radio). However if you read my google sheet you'll find instructions for backing up your current boot.img, your system and the stock recovery. If you do it correctly those files will suffice for recovering the ability of installing OTAs. No personal data will be backed up so maybe you want to share your backup with us afterwards.
There is a custom kernel for CM/AOSP roms which is said to repair the signal problems. As far as I read some sense rom users reported that flashing the stock boot.img recovered their signal. However this doesn't seem to work for every user. So you'll need to try by yourself.
Flippy498 said:
You can't backup your firmware (and that includes your radio). However if you read my google sheet you'll find instructions for backing up your current boot.img, your system and the stock recovery. If you do it correctly those files will suffice for recovering the ability of installing OTAs. No personal data will be backed up so maybe you want to share your backup with us afterwards.
Click to expand...
Click to collapse
Thank you so much! I have managed to find the guide you mentioned to backup the stock boot image, system image and recovery. By the looks of it the tab to the right is the guide to return my phone to its original state, which is good. I'm more than happy to share the backup once I do it.
Flippy498 said:
There is a custom kernel for CM/AOSP roms which is said to repair the signal problems. As far as I read some sense rom users reported that flashing the stock boot.img recovered their signal. However this doesn't seem to work for every user. So you'll need to try by yourself.
Click to expand...
Click to collapse
Okay, well I am planning on keeping s-on at this stage, so I'm left with Sense based ROMs I believe? I have read that LeeDroid is the best for battery life, does this sound right? If so I am unsure if I can flash it as it says "Please make sure you have the latest HTC Hima 3.35.XXX.XX Marshmallow firmware installed prior to installing this ROM" because my software number is 3.50.710.1?
Thanks again!
Da Doom Lord said:
Okay, well I am planning on keeping s-on at this stage, so I'm left with Sense based ROMs I believe? I have read that LeeDroid is the best for battery life, does this sound right? If so I am unsure if I can flash it as it says "Please make sure you have the latest HTC Hima 3.35.XXX.XX Marshmallow firmware installed prior to installing this ROM" because my software number is 3.50.710.1?
Click to expand...
Click to collapse
I've read that several times in the near past and I actually don't understand it. You never needed S-OFF for flashing none-sense based roms as long as I started using Android/HTC phones and that was back in 2012. Why do so many people think they need S-OFF for AOSP?
I personally prefer the Viper rom. But taste differs and in the end the best advice I can give is try it out by yourself. Everyone has different needs and is using his/her phone in a different way. The best rom for person a might be an awful choice for person b since he/she has completely different needs.
I can't tell you whether you can use Leedroid. Test it and report back. That's how xda works. You might be able to use it after you flashed your stock boot.img but I don't know whether you really are or not. The warning is written so that people don't start flashing that rom with a lower firmware version. On older HTC phones flashing an "older" rom has never been an issue on newer firmware versions whereas flashing a newer rom on an older firmware never goes well (even on the M9). However many things have changed since the M9. There is no hboot anymore, the Download Mode got introduced, google changed the way OTAs are checking whether your system is modified, and so on. (Just to mention a few changes.) Those issues with the lost signal didn't even exist on pre-3.x firmware versions of the M9. Therefore users like you who use a not so common firmware (in comparison to the user numbers of the most common firmware bases: international, taiwanese and the developer firmware) have no other choice but trying out by themselves or getting S-OFF and changing to a more common firmware.
Flippy498 said:
I can't tell you whether you can use Leedroid. Test it and report back. That's how xda works. You might be able to use it after you flashed your stock boot.img but I don't know whether you really are or not. The warning is written so that people don't start flashing that rom with a lower firmware version. On older HTC phones flashing an "older" rom has never been an issue on newer firmware versions whereas flashing a newer rom on an older firmware never goes well (even on the M9).
Click to expand...
Click to collapse
I have followed your guide and now have the latest stable LeeDroid ROM installed and TWRP. Just as I predicted the radio was not originally working. When I restored my stock boot.img from the original backup I performed it began to work. Thanks so much for your help! I'll upload the backup to cloud storage when I get access to a decent internet connection and then I'll share it to help others out.
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...
Hi everyone,
I would like to know if it is safe to unlock bootloader and flash a custom ROM under MIU 13.0.3 SKHEUXM ?
I've seen people having bugs, hence why I'm asking if anyone has given this a try ?
Furthermore, I was going to do this update in order for the firmware to be updated then switch to a custom ROM, but I could go for custom ROM first then flash the newest firmware (even if I'm more confident on the first option which should work out of the box, and preserve warranty in case something goes wrong during flashing firmware, always gotta keep fingers crossed).
Thanks for any help on this matter.
If you updated to the latest ROM, your firmware is updated along with it, there's no need to flash the firmware again seperately. Flash the ROM of your choosing, Magisk if you absolutely need it, and enjoy. Most ROMs these days also pass SafetyNet if you do not root your phone.
AkechiShiro said:
Hi everyone,
I would like to know if it is safe to unlock bootloader and flash a custom ROM under MIU 13.0.3 SKHEUXM ?
I've seen people having bugs, hence why I'm asking if anyone has given this a try ?
Furthermore, I was going to do this update in order for the firmware to be updated then switch to a custom ROM, but I could go for custom ROM first then flash the newest firmware (even if I'm more confident on the first option which should work out of the box, and preserve warranty in case something goes wrong during flashing firmware, always gotta keep fingers crossed).
Thanks for any help on this matter.
Click to expand...
Click to collapse
It's not very safe, you need to be careful.
Make sure your PC wouldn't crash or that your USB connection may be unstable.
Take your time in setting everything up and reading up some resources on the internet.
If the Flash-process aborts for whatever reason, do not reboot phone. Your phone may not be able to reboot back into Fastboot and turn black.
As for good resources of information, I recommend the YouTube Channel "Munchy". He covers Xiaomi Flashing very well. You can trust him.
https://www.youtube.com/channel/UCDSfvwvAsKE4Nrosu7bTbJw
You might also want to use a Custom ROM with passing SafetyNet, or to use Magisk Root. If SafetyNet fails, you can't use some apps.
I personally use Xiaomi.eu Weekly Android 12 with Magisk Root + SafetyNet Fix Module. No bugs, I'm happy
My only wish was that I had Over-The-Air updates. With most Custom ROMs, you unfortunately still have to download & flash the ZIP-file manually in TWRP Recovery.
Hi, a have recently purchased the XZ2 Compact single Sim model, it should arrive later this week. While waiting, I would appreciate everyone's opinion on which stock firmware version is best in terms of performance and battery life:
• Android 8 Oreo
• Android 9 Pie
• Android 10
Or if you guys haven't found a any difference, between firmware versions at all, then please comment below !
Thanks in advance.
David-538 said:
Hi, a have recently purchased the XZ2 Compact single Sim model, it should arrive later this week. While waiting, I would appreciate everyone's opinion on which stock firmware version is best in terms of performance and battery life:
• Android 8 Oreo
• Android 9 Pie
• Android 10
Or if you guys haven't found a any difference, between firmware versions at all, then please comment below !
Thanks in advance.
Click to expand...
Click to collapse
Latest 10 with eXistenZ patch - https://forum.xda-developers.com/t/rom-stock-xz2-xz2c-xz2p-existenz-quindim-v1-0-0-06-05-20.4095403/
levone1 said:
Latest 10 with eXistenZ patch - https://forum.xda-developers.com/t/rom-stock-xz2-xz2c-xz2p-existenz-quindim-v1-0-0-06-05-20.4095403/
Click to expand...
Click to collapse
Thanks for your suggestion, I just meant stock, without rooting, or installing any mods. Like has Sony made it worse with a9/a10 official update, or is there no major performance loss when upgrading ?
David-538 said:
Thanks for your suggestion, I just meant stock, without rooting, or installing any mods. Like has Sony made it worse with a9/a10 official update, or is there no major performance loss when upgrading ?
Click to expand...
Click to collapse
I have never used stock as-is, because of Sony bloatware, restrictions, etc, but I typically prefer stock UI over most custom ROM UIs, so if I can get eXistenZ, I will always go with it. @niaboc79 has been the master of Sony roms going back to at least 4.4. Between UI customization and under the hood type stuff, there's no better option I have found. With root and eXistenZ, the whole firmware is at your control...
If you're only interested in straight-stock vs. custom ROM, then custom ROM is by far better, but not sure why you would limit yourself to straight stock if that's the case, because you have to unlock bootloader and root to use custom ROM. The only advantage of straight stock is official support/security, which is arguably n/a in this case, since the last official update was 2 years ago...
levone1 said:
I have never used stock as-is, because of Sony bloatware, restrictions, etc, but I typically prefer stock UI over most custom ROM UIs, so if I can get eXistenZ, I will always go with it. @niaboc79 has been the master of Sony roms going back to at least 4.4. Between UI customization and under the hood type stuff, there's no better option I have found. With root and eXistenZ, the whole firmware is at your control...
If you're only interested in straight-stock vs. custom ROM, then custom ROM is by far better, but not sure why you would limit yourself to straight stock if that's the case, because you have to unlock bootloader and root to use custom ROM. The only advantage of straight stock is official support/security, which is arguably n/a in this case, since the last official update was 2 years ago...
Click to expand...
Click to collapse
Hi, ah yes, I also prefer rooting and custom roms, but there's chance the device won't be in unlocked, because I ordered it from Aliexpress, and it's the Japanese Docomo version. Anyway I also heard that some features and good photo quality, get lost when unlocking ? Is there a work around if the DRM keys get lost ?
David-538 said:
Hi, ah yes, I also prefer rooting and custom roms, but there's chance the device won't be in unlocked, because I ordered it from Aliexpress, and it's the Japanese Docomo version. Anyway I also heard that some features and good photo quality, get lost when unlocking ? Is there a work around if the DRM keys get lost ?
Click to expand...
Click to collapse
I don't think there's any such thing for this phone. Some have found a way to dump ta, but not to restore it, so not much use...
I upgraded to 10 to start with, then unlocked bl, etc. I think that's the best way. There's much discussion in the forums about camera function and drm in regards to 8 and 9, (ask @MartinX3 or @Pandemic), and seems like there may be different things you can do...
I'm not so hung up on the finer aspects of camera functionality. I think the difference is pretty subtle. Camera is good for me, (probably better on stock with unlocked bl than on custom/AOSP).
levone1 said:
I don't think there's any such thing for this phone. Some have found a way to dump ta, but not to restore it, so not much use...
I upgraded to 10 to start with, then unlocked bl, etc. I think that's the best way. There's much discussion in the forums about camera function and drm in regards to 8 and 9, (ask @MartinX3 or @Pandemic), and seems like there may be different things you can do...
I'm not so hung up on the finer aspects of camera functionality. I think the difference is pretty subtle. Camera is good for me, (probably better on stock with unlocked bl than on custom/AOSP).
Click to expand...
Click to collapse
Okay, thanks for the info. I'm new to Sony devices lol. Well I always wanted to try out a sony device. Anyway is 960fps video recording still there ? After unlocking your bootloader ?
levone1 said:
I have never used stock as-is, because of Sony bloatware, restrictions, etc, but I typically prefer stock UI over most custom ROM UIs, so if I can get eXistenZ, I will always go with it. @niaboc79 has been the master of Sony roms going back to at least 4.4. Between UI customization and under the hood type stuff, there's no better option I have found. With root and eXistenZ, the whole firmware is at your control...
If you're only interested in straight-stock vs. custom ROM, then custom ROM is by far better, but not sure why you would limit yourself to straight stock if that's the case, because you have to unlock bootloader and root to use custom ROM. The only advantage of straight stock is official support/security, which is arguably n/a in this case, since the last official update was 2 years ago...
Click to expand...
Click to collapse
Just flashed eXistenZ after seeing your opinion. But help me out... How do i know the flash is properly done if there is no kernel brand on device stats... Weird
Purplearyes said:
Just flashed eXistenZ after seeing your opinion. But help me out... How do i know the flash is properly done if there is no kernel brand on device stats... Weird
Click to expand...
Click to collapse
...
Purplearyes said:
Just flashed eXistenZ after seeing your opinion. But help me out... How do i know the flash is properly done if there is no kernel brand on device stats... Weird
Click to expand...
Click to collapse
Not sure what you mean by kernel brand, but you know if flashed properly because the ui and options will be drastically different with eXistenZ compared to stock. If everything's the same, then it's not flashed.
levone1 said:
Not sure what you mean by kernel brand, but you know if flashed properly because the ui and options will be drastically different with eXistenZ compared to stock. If everything's the same, then it's not flashed.
Click to expand...
Click to collapse
Yes i just realized the flash didn't went through. im experiencing many issues. Firstly twrp is not flashing anything always some error of storage access or something. then i try to flash on los recovery, and it works for lineage perfect flash, but for existenz stock zip it flashes everything no errors but doesn't change anything on the stock rom (.618 clean install) i can't seem to figure it out...
levone1 said:
Not sure what you mean by kernel brand, but you know if flashed properly because the ui and options will be drastically different with eXistenZ compared to stock. If everything's the same, then it's not flashedalso
levone1 said:
I have never used stock as-is, because of Sony bloatware, restrictions, etc, but I typically prefer stock UI over most custom ROM UIs, so if I can get eXistenZ, I will always go with it. @niaboc79 has been the master of Sony roms going back to at least 4.4. Between UI customization and under the hood type stuff, there's no better option I have found. With root and eXistenZ, the whole firmware is at your control...
If you're only interested in straight-stock vs. custom ROM, then custom ROM is by far better, but not sure why you would limit yourself to straight stock if that's the case, because you have to unlock bootloader and root to use custom ROM. The only advantage of straight stock is official support/security, which is arguably n/a in this case, since the last official update was 2 years ago...
Click to expand...
Click to collapse
I did some research and from what is logged on existenz page it includes nothing more than UI customizations? Am i missing something. How can this stock patch be the best for you if it only does UI changes..?
Click to expand...
Click to collapse
Purplearyes said:
Yes i just realized the flash didn't went through. im experiencing many issues. Firstly twrp is not flashing anything always some error of storage access or something. then i try to flash on los recovery, and it works for lineage perfect flash, but for existenz stock zip it flashes everything no errors but doesn't change anything on the stock rom (.618 clean install) i can't seem to figure it out..
Click to expand...
Click to collapse
- Which version of TWRP? Make sure you are using the right one. Should be this one - https://forum.xda-developers.com/xperia-xz2/development/recovery-twrp-3-3-1-0-t4074305
- Did you follow this, (from eXistenZ thread):
Flash latest android 10 firmware with Newflasher and boot it once.
Reboot in bootloader mode with adb (adb reboot boolloader) and boot TWRP (see TWRP thread for instructions).
Inside TWRP, go in settings and uncheck unmount system before flashing.
Mount system partition and Flash eXistenZ Quidim cleaner.
Boot once, it shouldn't reach pin code screen, reboot in bootloader mode with adb.
Boot TWRP, mount system partition and flash the rom.
Flash Magisk.
(e.g. - make sure to boot once before flashing, use adb for bootloader mode, check system in TWRP, etc...)
levone1 said:
- Which version of TWRP? Make sure you are using the right one. Should be this one - https://forum.xda-developers.com/xperia-xz2/development/recovery-twrp-3-3-1-0-t4074305
- Did you follow this, (from eXistenZ thread):
Flash latest android 10 firmware with Newflasher and boot it once.
Reboot in bootloader mode with adb (adb reboot boolloader) and boot TWRP (see TWRP thread for instructions).
Inside TWRP, go in settings and uncheck unmount system before flashing.
Mount system partition and Flash eXistenZ Quidim cleaner.
Boot once, it shouldn't reach pin code screen, reboot in bootloader mode with adb.
Boot TWRP, mount system partition and flash the rom.
Flash Magisk.
(e.g. - make sure to boot once before flashing, use adb for bootloader mode, check system in TWRP, etc...)
Click to expand...
Click to collapse
I used 3.4.00 twrp, maybe should try 3.3.10. Also i flashed .618 which is 10 though not the latest but it should be the same thing.
The rom seems to flash, because i get the existenz custom settings on phone settings, idk if that is all it does.