Related
I just order Mi 5S yesterday from AliExpress. I Asked them to not flash any custom ROM and keep stock. Seller confirmed but I'm still a bit suspicious they may flash custom ROM. Is/are there any way/s to confirm that one has stock or custom ROM installed on the device?
literadesign said:
I just order Mi 5S yesterday from AliExpress. I Asked them to not flash any custom ROM and keep stock. Seller confirmed but I'm still a bit suspicious they may flash custom ROM. Is/are there any way/s to confirm that one has stock or custom ROM installed on the device?
Click to expand...
Click to collapse
Simple. Once you get your device, check which version is installed by going into Settings / About Phone.
Then simply check http://en.miui.com/extra.php?mod=rom/download&r=314&mobile=no and compare. If the version installed doesn't match the ones in the link, then it isn't an official rom.
dgrasley said:
Simple. Once you get your device, check which version is installed by going into Settings / About Phone.
Then simply check http://en.miui.com/extra.php?mod=rom/download&r=314&mobile=no and compare. If the version installed doesn't match the ones in the link, then it isn't an official rom.
Click to expand...
Click to collapse
Is it truly that easy. Couldn't one create a ROM that would have the same version signature?
literadesign said:
Is it truly that easy. Couldn't one create a ROM that would have the same version signature?
Click to expand...
Click to collapse
I'm pretty sure you can, so it's safer to flash an original ROM package from miui if buying from 3rd party vendors, they might install mal/spyware
literadesign said:
I just order Mi 5S yesterday from AliExpress. I Asked them to not flash any custom ROM and keep stock. Seller confirmed but I'm still a bit suspicious they may flash custom ROM. Is/are there any way/s to confirm that one has stock or custom ROM installed on the device?
Click to expand...
Click to collapse
literadesign said:
Is it truly that easy. Couldn't one create a ROM that would have the same version signature?
Click to expand...
Click to collapse
Well, it's that easy to check which version you have and if that version number is official or not.
If you are that concerned about it, flash an official version.
You can check if your bootloader is unlocked. If it is, you got a custom one. If it isn't, you have an official rom, or they were able to change it in the production of the phone itself (as the bootloader only allows correctly signed roms).
patoberli said:
You can check if your bootloader is unlocked. If it is, you got a custom one. If it isn't, you have an official rom, or they were able to change it in the production of the phone itself (as the bootloader only allows correctly signed roms).
Click to expand...
Click to collapse
how can one check whether the bootloader is locked?
If you have ADB experience, this is the command:
fastboot oem device-info
Source and complete manual:
http://en.miui.com/thread-279195-1-1.html
patoberli said:
You can check if your bootloader is unlocked. If it is, you got a custom one. If it isn't, you have an official rom, or they were able to change it in the production of the phone itself (as the bootloader only allows correctly signed roms).
Click to expand...
Click to collapse
This is not true. They can also flash a Shop-ROM with EDL flashing mode. I also have a custom ROM on my mi 5s (8.0.10.0.0, with google play and many languages) and bootloader was locked.
If you have original ROM you will only have chinese and english language. Also there should be no google software at all (no google play, no google services). If it is so, and you have version "8.0.10.0(MAGCNDH)" then it shhould be original firmware from Xiaomi.
Oh wow, didn't know that they can do this.
So my phone came with this version:
MIUI 8.0.15.0(MAGCNDI)
Android version 6.0.1 MXB48T
Interesting enough this version isn't on the miui.com for download... Is it legit or not?
Mine has the same version, opened this thread: http://en.miui.com/thread-417953-1-1.html
You might also want to add a picture there
patoberli said:
Mine has the same version, opened this thread: http://en.miui.com/thread-417953-1-1.html
You might also want to add a picture there
Click to expand...
Click to collapse
I did.
Sent from my Galaxy Nexus using Tapatalk
Great thanks. So far it looks like it's an official factory ROM, at least mine looks like it was never tampered with. Let's wait and see what their forum admins think of this. You also don't get the OTA to 8.0.17.0?
patoberli said:
Great thanks. So far it looks like it's an official factory ROM, at least mine looks like it was never tampered with. Let's wait and see what their forum admins think of this. You also don't get the OTA to 8.0.17.0?
Click to expand...
Click to collapse
I already flashed the 6.11.10 developer ROM because you apparently need dev ROM to unlock. Now waiting for my permission to unlock from Xiaomi Gods. Is it likely to get denied or granted?
I think it's always granted, but it can take up to 10 days.
Could you do me a favor, can you test if Pokemon Go runs on your mobile now?
Also can you check if this app gives you a Pass or Fail?
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
This checks if your mobile is still SafetyNet conform, which means all apps, even banking ones, should start.
patoberli said:
Great thanks. So far it looks like it's an official factory ROM, at least mine looks like it was never tampered with. Let's wait and see what their forum admins think of this. You also don't get the OTA to 8.0.17.0?
Click to expand...
Click to collapse
Maybe a question for those that have used MIUI for a longer time... The 8.0.15.0 version had monochromatic icons in settings menu, but when I flashed latest official Dev ROM 6.11.10, those icons are now coloured. So if icons used to be monochromatic up until some past version, than this supposedly newest version 8.0.15.0 can't be future unless Xiaomi decided for whatever reason to go from mono, to colours and back to mono icons.
literadesign said:
I already flashed the 6.11.10 developer ROM because you apparently need dev ROM to unlock. Now waiting for my permission to unlock from Xiaomi Gods. Is it likely to get denied or granted?
Click to expand...
Click to collapse
My phone came with the box unsealed and a fake ROM installed which I wasn't very happy about. I applied for unlocking the first day I got the phone and about 15minutes after submitting, received approval to unlock! The reason I stated was to flash an official ROM as I was unhappy with the vendor ROM.
I had read somewhere that others were successful unlocking without a developer ROM and after initial difficulties getting to 50% before failing, read another post on the Miui forums about the need to do a factory reset and then immediately sign in to your Miui account accepting all options for sync, Mi Cloud, backup etc. I did this and sure enough, the process completed and the bootloader was unlocked!
Hi guys, I'm going to buy a OnePlus 5T, coming from a Motorola Moto X Play.
I used to do basic and old modding, without a need to think about project Treble or encrypt/decrypt.
I know now it is project Treble enabled also in stable channel, so now I would like to take away some doubts.
I actively watched threads and updates but I'm really confused by a big amount of things to consider, like:
- Do I need a Treble compatible Magisk?
- Do I need a Treble compatible TWRP?
- What's "no-verity" useful for? Why could I need to decrypt my OP5T?
- Do I have to follow a specific procedure to flash official updates if I have a custom recovery and Magisk installed?
So... A good list of ToDo, things I need to know before bricking the new beautiful entry is the request :angel:
If you can help me also with links, I'll appreciate.
nplezka said:
- Do I need a Treble compatible Magisk?
- Do I need a Treble compatible TWRP?
- What's "no-verity" useful for? Why could I need to decrypt my OP5T?
- Do I have to follow a specific procedure to flash official updates if I have a custom recovery and Magisk installed?
Click to expand...
Click to collapse
This guide is great to give you a start.
- No, you don't need Treble compatible Magisk. Magisk 16.0 works fine.
- Yes, you need the latest blu_spark or codeworkx TWRP. You can get to them from the guide above. Don't use the official TWRP btw.
- (I'm not very knowledgeable about this) I believe no-verity is to keep the device decrypted. I'm running it encrypted at the moment and see no reason to decrypt the phone.
- Kinda specific but nothing special. Here's my procedure (I'm running stable OOS ROM):
Download Full ZIP file (~1.6 GiB), not the OTA one. If your phone is rooted, system update will download the full file (instead of the ota); or you can use Oxygen Updater from the app store.
Change lockscreen lock from passcode to none (because my TWRP can't run properly with passcode. I have heard that many people don't need to do this)
Reboot to TWRP recovery
Flash Full Zip and Magisk in that order
(Some people say clear cache/dalvik before and after flashing, idk)
Reboot to system and change lock screen back to normal.
I think there's no big to do stuff with oneplus if you only do basic modding but I run my device fairly basic anyway so others can chime in with more advanced stuffs.
squaresmile said:
[*]Change lockscreen lock from passcode to none (because my TWRP can't run properly with passcode. I have heard that many people don't need to do this)
Click to expand...
Click to collapse
Maybe it's a stupid question, but I never had a pin or password on my lockscreen, and for sure I will simply use the fingerprint (or face-unlock? ?) on my future OP5T, so this point is only for who use a password/pin/sequence, right?
nplezka said:
Maybe it's a stupid question, but I never had a pin or password on my lockscreen, and for sure I will simply use the fingerprint (or face-unlock? ) on my future OP5T, so this point is only for who use a password/pin/sequence, right?
Click to expand...
Click to collapse
Pretty sure you need password/pin to use fingerprint/face unlock. However, I have heard that others can go to TWRP fine with a password/pin so you probably will be fine. I must have messed up somewhere I'm too lazy to fix now.
squaresmile said:
Pretty sure you need password/pin to use fingerprint/face unlock. However, I have heard that others can go to TWRP fine with a password/pin so you probably will be fine. I must have messed up somewhere I'm too lazy to fix now.
Click to expand...
Click to collapse
Do you think I have to do something in particular when I'll update to the OOS update with Treble, starting from the in-built firmware (don't know the exact version, but I'm talking about Nougat)? Or I can update normally?
It'll be the first thing I'll do, before unlocking and rooting. :cyclops:
nplezka said:
Do you think I have to do something in particular when I'll update to the OOS update with Treble, starting from the in-built firmware (don't know the exact version, but I'm talking about Nougat)? Or I can update normally?
It'll be the first thing I'll do, before unlocking and rooting. :cyclops:
Click to expand...
Click to collapse
Probably not if you follow the updater in settings. I would expect the stock update process to be pretty stable.
Generic System Image, as we know, is the production of Project Treble. Since the phone has twrp now, how can I install it? Or has anyone tried so?
zhufucdev said:
Generic System Image, as we know, is the production of Project Treble. Since the phone has twrp now, how can I install it? Or has anyone tried so?
Click to expand...
Click to collapse
no, if you try ,you will meet bootloop problem. because of android 10 seciurity!
Does GSI ROMs work now?
Hello,
I have a device that I obtained through beta testing that has not been released yet. I am allowed to keep the device now that testing is over. I am not happy with the stock rom and some of the apps it forces you to keep. I cannot remove them through ABD either. There is no stock ROM image available yet. Therefore, I cannot port TWRp or root.
I stumbled on project treble. I ran treble check and it says my phone is supported as it came with android 11. It supports systemless updates and has A/B system partition. I really like stock android ASOP. Is there anyway I can flash a generic image? What's the odds of it working correctly? Since there is no image available yet and I cannot port TWRP I have to worrying about not being able to recover the device if things go wrong. I know you can flash without TWRP which is why I decided to ask about this. Would I have a better chance flashing roms for supported devices with similar hardware? How should I proceed?
Thanks,
Rocky
as long as you have a compatible custom recovery AND the stock rom in case something go wrong, you can flash any GSI according to your device's architecture
Roizoulou said:
as long as you have a compatible custom recovery AND the stock rom in case something go wrong, you can flash any GSI according to your device's architecture
Click to expand...
Click to collapse
Since it is a beta unit I have neither as it has not been officially released. I have never flashed one of these roms so I do not know how well they work after flashing. I know the device has a pretty popular SOC which is a snapdragon 750g so I would assume if a gai runs good on another device using the 750g then it should work.
bigroc2223 said:
Since it is a beta unit I have neither as it has not been officially released. I have never flashed one of these roms so I do not know how well they work after flashing. I know the device has a pretty popular SOC which is a snapdragon 750g so I would assume if a gai runs good on another device using the 750g then it should work.
Click to expand...
Click to collapse
best you can do is dump the whole rom, make a backup before going any further
Roizoulou said:
best you can do is dump the whole rom, make a backup before going any further
Click to expand...
Click to collapse
I don't think I can dump it without root right?
bigroc2223 said:
I don't think I can dump it without root right?
Click to expand...
Click to collapse
an unlocked bootloader first and just search for how to dump system on google. it usually just need a pc and ADB
bigroc2223 said:
I don't think I can dump it without root right?
Click to expand...
Click to collapse
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
Roizoulou said:
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried this before it requires root. I just double checked and the prereqs say root required too. This sucks because the device has decent specs. It's just the ROM and software on it are crappy. After doing some reading the biggest thing I'm worried about is flashing and not having mobile data since it is a 5g phone. I read about someone else flashing and not being able to get their mobile data to work.
bigroc2223 said:
I tried this before it requires root. I just double checked and the prereqs say root required too. This sucks because the device has decent specs. It's just the ROM and software on it are crappy. After doing some reading the biggest thing I'm worried about is flashing and not having mobile data since it is a 5g phone. I read about someone else flashing and not being able to get their mobile data to work.
Click to expand...
Click to collapse
what is the device?
Roizoulou said:
what is the device?
Click to expand...
Click to collapse
It's a beta device from TCL. It has not been released yet. I read that phh GSI should be compatible with all android phones with treble support. Therefore, I think I might just go for it. The only thing is if I end up with a bug I more than likely will probably have to figure it out on my own.
bigroc2223 said:
It's a beta device from TCL. It has not been released yet. I read that phh GSI should be compatible with all android phones with treble support. Therefore, I think I might just go for it. The only thing is if I end up with a bug I more than likely will probably have to figure it out on my own.
Click to expand...
Click to collapse
just try phh's first and if you encounter issues, try other custom roms
Roizoulou said:
just try phh's first and if you encounter issues, try other custom roms
Click to expand...
Click to collapse
I think I might of found a solution. I am pretty sure there is a way to boot a ROM before flashing it. I could of sworn I read this somewhere. It was an adb command. It allowed you too boot the ROM instead of flashing it. This would allow me to preview the ROM before officially flashing it to the device. I just cannot remember where I saw this at or the command.
My goal is to get a working gsi installed. From there I would like to get TWRP flashed on the device so it can be rooted. If I would need to port TWRP I think I could figure it out. This way when the device is officially released it will have TWRP ready to go for it. Also, since it will have TWRP I will be able to start porting roms as soon as they release the system image.
bigroc2223 said:
I think I might of found a solution. I am pretty sure there is a way to boot a ROM before flashing it. I could of sworn I read this somewhere. It was an adb command. It allowed you too boot the ROM instead of flashing it. This would allow me to preview the ROM before officially flashing it to the device. I just cannot remember where I saw this at or the command.
My goal is to get a working gsi installed. From there I would like to get TWRP flashed on the device so it can be rooted. If I would need to port TWRP I think I could figure it out. This way when the device is officially released it will have TWRP ready to go for it. Also, since it will have TWRP I will be able to start porting roms as soon as they release the system image.
Click to expand...
Click to collapse
like DSU loader?
Roizoulou said:
like DSU loader?
Click to expand...
Click to collapse
Never heard of that this was just an adb command.
I just downloaded ASOP 11.0 v309. Treble info says my device requires system-arm64-ab.img.xz. So I downloaded system-roar-arm64-ab-gapps.img.xz and system-roar-arm64-ab-vanilla.ikg.gz so hopefully those are the right ones. One has Gapps and one does not. Was going to flash the Gapps version first and see how things go. Then if need be flash vanilla.
I got a problem with phone calls. When I dial out I get call ended. Incoming calls I can hear them ring but get no way to answer. Also I am not getting text messages.
Roizoulou said:
like DSU loader?
Click to expand...
Click to collapse
I got it all working bro thanks for your help
bigroc2223 said:
I got it all working bro thanks for your help
Click to expand...
Click to collapse
gapps or vanilla?
Roizoulou said:
gapps or vanilla?
Click to expand...
Click to collapse
I was able to get them both to work. However, I am trying to use the gapps version, but I am getting an error that the device is not google certified. I cannot find a workaround unless I unroot which I do not want to do =(
bigroc2223 said:
I was able to get them both to work. However, I am trying to use the gapps version, but I am getting an error that the device is not google certified. I cannot find a workaround unless I unroot which I do not want to do =(
Click to expand...
Click to collapse
rooted with magisk?
Roizoulou said:
rooted with magisk
Click to expand...
Click to collapse
It comes rooted with phh superuser. I'm trying to find a way to pull my boot.img from the device so I can use it to flash magisk since it has a workaround for non Google certified devices.
I think I understand the idea behind the device-specific Treble system, and the device-agnostic GIS images, which can work on any phone that has Treble. The app "Treble Check" says that the Sony Xperia 10 III is fully supported.
Here's my questions / educated guesses, please tell me if they're wrong or right:
1. This phone already comes with a Treble-compliant hardware layer (kernel+drivers) and GSI-compliant user-facing ROM, directly from Sony.
2. I can install any other GSI ROM (or from XDA) as long as it's an A/B arm64 ROM, and the hardware should work perfectly.
3. Can the phone still get OTA vendor updates for the hardware stuff after I unlock bootloader/install 3rd party GIS, or do I have to get the new images and flash them manually? Or do I get cut off from them altogether?
4. The original bootloader can take commands from the standard fastboot util in the Android SDK Platform Tools.
5. I understand I need to unlock the bootloader in order to be able to flash anything, but why is it necessary to overwrite the vbmeta partition?
6. Is the procedure to get Magisk working still patching the bootloader, regardless what GSI ROM I install?
7. Did anybody pass Safety Net with Magisk and a 3rd-party GIS ROM? Can it be passed anymore after unlocking bootloader?
8. I see there's no TWRP recovery for this device. Does it matter? Are there alternatives? In theory, if I have Magisk->root I can do pretty much anything so it doesn't sound like a big deal.
wirespot said:
1. This phone already comes with a Treble-compliant hardware layer (kernel+drivers) and GSI-compliant user-facing ROM, directly from Sony.
Click to expand...
Click to collapse
Yes.
wirespot said:
2. I can install any other GSI ROM (or from XDA) as long as it's an A/B arm64 ROM, and the hardware should work perfectly.
Click to expand...
Click to collapse
In theory. In practice it still depends on how the GSI ROM was implemented, there can still be issues.
wirespot said:
3. Can the phone still get OTA vendor updates for the hardware stuff after I unlock bootloader/install 3rd party GIS, or do I have to get the new images and flash them manually? Or do I get cut off from them altogether?
Click to expand...
Click to collapse
Not totally sure about this one. I think you don't get to install OTA updates anymore. You can probably download a new firmware with XperiFirm and flash pieces of it but no idea how that would work or what would happen.
wirespot said:
4. The original bootloader can take commands from the standard fastboot util in the Android SDK Platform Tools.
Click to expand...
Click to collapse
Yes. Sony did a great job going for standard things.
wirespot said:
5. I understand I need to unlock the bootloader in order to be able to flash anything, but why is it necessary to overwrite the vbmeta partition?
Click to expand...
Click to collapse
The original vbmeta partition contains a mechanism that checks for the other partitions to not be modified. The image downloaded from Google disables that mechanism, so you can put whatever you want on any partition.
wirespot said:
6. Is the procedure to get Magisk working still patching the bootloader, regardless what GSI ROM I install?
Click to expand...
Click to collapse
Yes, it's for the best. A large amount of what Magisk does is based on it being "hidden" from the regular system. Not just for hiding from SafetyNet, since you may not care about that with a 3rd party GSI ROM, but because keeping system modifications separate and keeping the original ROM is a very, very good practice.
wirespot said:
7. Did anybody pass Safety Net with Magisk and a 3rd-party GIS ROM? Can it be passed anymore after unlocking bootloader?
Click to expand...
Click to collapse
You can pass SafetyNet on the stock ROM, with unlocked bootloader and boot image patched to load Magisk. See my how to guide. I don't know about 3rd party GIS ROMs.
wirespot said:
8. I see there's no TWRP recovery for this device. Does it matter? Are there alternatives? In theory, if I have Magisk->root I can do pretty much anything so it doesn't sound like a big deal.
Click to expand...
Click to collapse
I've looked into this some more. The biggest downsides seem to be inability to restore backups of the userdata, and inability to disable problematic Magisk modules. There are modules such as Magisk Bootloop Protector which will disable all modules if it detects a bootloop, but if the problem is not a bootloop and still prevents your access you're out of luck...
Please feel free to add more info.