[Solved] Update to OOS Oreo with Unlocked bootloader - OnePlus 5 Guides, News, & Discussion

Hello everyone,
I'm trying to update my OP5 to OOS Oreo offcial ROM, unfortunately TWRP returns systematcally an Error 7 and nothing occurs.
I guess its due to my unlocked bootloader. Does anyone knows :
- If it's the reason for this Error 7
- If there is a way to update while keeping bootloader unlocked ?
I definitely want to avoid the whole process of backuping everything on my computer, locking BL, installing, unlocking BL once again :silly:
Thanks per advance !

eriadamord said:
Hello everyone,
I'm trying to update my OP5 to OOS Oreo offcial ROM, unfortunately TWRP returns systematcally an Error 7 and nothing occurs.
I guess its due to my unlocked bootloader. Does anyone knows :
- If it's the reason for this Error 7
- If there is a way to update while keeping bootloader unlocked ?
I definitely want to avoid the whole process of backuping everything on my computer, locking BL, installing, unlocking BL once again :silly:
Thanks per advance !
Click to expand...
Click to collapse
Hei dude.. you dont need to, just flash codeworkx twrp and you good to go..
Sent from my [device_name] using XDA-Developers Legacy app

akuadi said:
Hei dude.. you dont need to, just flash codeworkx twrp and you good to go..
Click to expand...
Click to collapse
Thanks a lot I'll try this asap ! Do you know if I can just adb push this version of TWRP over the existing one or is-it a specific process ?

eriadamord said:
Thanks a lot I'll try this asap ! Do you know if I can just adb push this version of TWRP over the existing one or is-it a specific process ?
Click to expand...
Click to collapse
No specific process, same as usual.. Its easier to do it with adb fastboot command..
Sent from my [device_name] using XDA-Developers Legacy app

Flashing codeworkx twrp worked for me. I was getting the same errors as you.

Ok I did it but I might have done some incredible mess :
- flash recommend TWRP over current one
- /!\ forgot to wipe cache & factory reset
- installed new rom
- rom was not booting
I forced reboot and went to TWRP. It did not asked me password for decryption and everything was crypted
I reboot into TWRP once again > partition size was 0Ko > everything was gone
Reboot once again > no recovery accessible > phone bricked
I used the unbrick tool found on XDA and worked like a charm. Now everything is lost but phone OK. Unfortunately I was totally stupid and left Nandroid & Titanium Backup on my phone internal memory
I don't know if the whole **** was due to my error of non wiping correctly or flashing TWRP or encryption. If someone has a clue it could be interesting for further bad experience
By the was it's good to know that the unbrick tool available on the forum is working ! I highly recommend you to take it as a backup before the link is dead (I had this issue on OPX)

https://forum.xda-developers.com/oneplus-5/how-to/guide-upgrade-4-5-15-rooted-encrypted-5-t3730891

zdimension said:
https://forum.xda-developers.com/oneplus-5/how-to/guide-upgrade-4-5-15-rooted-encrypted-5-t3730891
Click to expand...
Click to collapse
Argh, unfortunately too late for me but good for next time !
Thanks
Edit : subject solved, thanks for your help !

Related

[Q] is there a factory restore (not reset) available?

I'd like to do a clean re-install of the OS before moving everything over to the phone ... but I don't see any downloads for the 3T on the OP downloads page?
http://downloads.oneplus.net/
zim2dive said:
I'd like to do a clean re-install of the OS before moving everything over to the phone ... but I don't see any downloads for the 3T on the OP downloads page?
http://downloads.oneplus.net/
Click to expand...
Click to collapse
Not that I know of. Im bricked until they release them
Atlantian said:
Not that I know of. Im bricked until they release them
Click to expand...
Click to collapse
Dare I ask what went wrong?
I was going to unlock the bootloader (since it would require a full wipe if I waited and did it later), but otherwise stop there (I don't think changing recovery or rooting result in any need to wipe)
There is a full OTA zip in the 2nd post of the TWRP thread. This may solved your problem. But I do suggest you read the whole thread, as there maybe info that regard to your bootloader issue. I noticed that some of the OP3T came with OOS 3.5.1, which have issue w/ custom recovery. So you have to upgrade to 3.5.3.
PS: there is this full backup available also.
someone0 said:
There is a full OTA zip in the 2nd post of the TWRP thread. This may solved your problem. But I do suggest you read the whole thread, as there maybe info that regard to your bootloader issue. I noticed that some of the OP3T came with OOS 3.5.1, which have issue w/ custom recovery. So you have to upgrade to 3.5.3.
PS: there is this full backup available also.
Click to expand...
Click to collapse
I don't have the phone yet ..just ordered it but I'm interested..... how to install the ota zip on stock recovery??...
Sorry for the#noob guestion # but I'm coming from lg and op3 is totally new for me....
cultofluna said:
I don't have the phone yet ..just ordered it but I'm interested..... how to install the ota zip on stock recovery??...
Sorry for the#noob guestion # but I'm coming from lg and op3 is totally new for me....
Click to expand...
Click to collapse
After mucking around with TWRP/Root, I decided I wanted to try the plain vanilla SafetyNet-compliant OxygenOS experience. In TWRP, I flashed the 3.5.3 OTA from here. I rebooted my phone into Fastboot and relocked the bootloader, then rebooted back into OxygenOS. I think relocking the bootloader and flashing the OTA are interchangeable.
Also, from what I recall, if you want to flash the file through the stock recovery, have the file downloaded to the root of your internal storage partition and name it ota.zip. Either download it while in the OS, or use Fastboot mode and use adb push to upload it from your computer to your phone through USB. Reboot into Recovery and there should be an option to update.

Twrp problem please help!

So let me explain the whole story, so a couple days ago i install OOS 4.0 on my Oneplus 3T and tried to root it, bearing in mind i was already rooted when i upgraded and I lost my root privileges. So then when i tried to re-root my phone it ahs come up with "dm-verity has not started in enforcing mode and may not work properly", so a bit weird but then i tried to install TWRP and when i booted into TWRP, it just stayed at flash screen of TWRP and wouldn't initialize. I have being trying ever since, factory resetting my phone, re-root etc. Please help me!
I CANNOT BOOT INTO TWRP, IF YOU WERE GOING TO SAY THAT!
Boot it into a boot loader and use this :
https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
Choose option 4 and make sure you are unlocked.
Choose option 7 and wait a few moments to see if that works. If not try the UnBrick tool.
How long have you been waiting on the TWRP startup screen? You do know it takes a long time to startup using F2FS and encryption on data partition, up to a minute from what I've heard.
pitrus- said:
How long have you been waiting on the TWRP startup screen? You do know it takes a long time to startup using F2FS and encryption on data partition, up to a minute from what I've heard.
Click to expand...
Click to collapse
I'd normally wait around 5 minutes
UPDATE:So i just booted into TWRP and have been waiting around one minute and it is still on the splash screen.
Look at this:
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
DarqAnshin said:
Look at this:
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
I'll check it out.
DerpDiamonds said:
I'll check it out.
Click to expand...
Click to collapse
It didn't work
is your bootloader locked or unlocked?
This question seems to keep repeating itself due to missing information on TWRP post about the latest official version being incompatible with OOS 4 encryption method, but that is the explanation. There is a beta release of TWRP in post 550 in that thread that is supposed to fix this.
DerpDiamonds said:
I'll check it out.
Click to expand...
Click to collapse
pitrus- said:
This question seems to keep repeating itself due to missing information on TWRP post about the latest official version being incompatible with OOS 4 encryption method, but that is the explanation. There is a beta release of TWRP in post 550 in that thread that is supposed to fix this.
Click to expand...
Click to collapse
Oh i get it now, thanks i'll wait for TWRP to update. Thanks!

[SOLVED] Phone changed the model in TWRP

Hey,
I have question about a problem I have.
So I tried to install the latest open beta version (beta 17) on my OnePlus 3T through TWRP.
This didn't worked because of ERROR: 7.
I found some solutions to fix ERROR 7 but it doesn't worked with this OS.
I tried some things like updating TWRP and installing the Oxygen recovery. I messed some things up. I deleted my OS from my device accidentally.
I solved the problem and was able to install the latest stable OS without problems.
Then I tried to install ResurrectionRemix-N for OP3T and I got the ERROR 7 again. but it said:
E3004: This package is for device: OnePlus3T, oneplus3t; this device is Oneplus3.
The thing is, it is an OnePlus 3T.
I don't know why and how it changed. The TWRP is for OP3T.
In the settings it says that the Build-Number is: ONEPLUS A3003_28_171012.
So I don't know. The default device name was OnePlus 3T.
Later I got an automatic email from Google because I logged in on an "new" device. But here they say that it is an OP3.
I would like to change it, but I don't know how.
I thought I can just change someting in the build.prop, but I didn't tried it yet.
Hopefully someone can help me.
-Fun4Jan
Okay so, I went in the build.prop and this is what I found:
ro.build.product=OnePlus3
ro.build.user=OnePlus
ro.build.flavor=OnePlus3-user
ro.build.description=OnePlus3-user 7.1.1 NMF26F 136 dev-keys
ro.common.soft=OnePlus3
ro.display.series=OnePlus 3T
ro.build.oemfingerprint=7.1.1/NMF26F/10122113:user/release-keys
[...]
ro.build.ota.versionname=OnePlus3TOxygen_28_1710122300
ro.build.version.ota=OnePlus3TOxygen_28.A.57_GLO_057_1710122300
So do you think I can just change it in the build.prop?
Yes, you can change it in the build.prop.
please try changing it and report us back.
akash.galaxy07 said:
Yes, you can change it in the build.prop.
please try changing it and report us back.
Click to expand...
Click to collapse
So I changed it and tried to install it but failed. It tells me that it is an OP3
Try the Qualcomm MSM Tool and try resetting your device completely as instructed on the Unbrick guide. Looks like you installed a corrupted Open Beta package, and something from Bootloader configuration went completely haywire. You can backup your Internal Storage since you have TWRP access.
Good Luck!
Have you tried using TWRP version 3.1.1-0?
Fun4Jan said:
So I changed it and tried to install it but failed. It tells me that it is an OP3
Click to expand...
Click to collapse
With oreo use this TWRP https://forum.xda-developers.com/devdb/project/dl/?id=27068
after flash again beta 17
przemcio510 said:
Have you tried using TWRP version 3.1.1-0?
Click to expand...
Click to collapse
I tried it with TWRP 3.1.1-2 for the OnePlus 3t
thes3usa said:
Try the Qualcomm MSM Tool and try resetting your device completely as instructed on the Unbrick guide. Looks like you installed a corrupted Open Beta package, and something from Bootloader configuration went completely haywire. You can backup your Internal Storage since you have TWRP access.
Good Luck!
Click to expand...
Click to collapse
Okay, I will try it. I hope it works
kob72 said:
With oreo use this TWRP https://forum.xda-developers.com/devdb/project/dl/?id=27068
after flash again beta 17
Click to expand...
Click to collapse
Can you Explain it to me a bit detailed please.
Fun4Jan said:
Okay, I will try it. I hope it works
Click to expand...
Click to collapse
So I tried it with this instruction: http://www.androidbrick.com/oneplus-one-two-3-3t-5-mega-unbrick-guide-twrp-flashing/
I did it like it says but some things were different and I think it was because my phone worked and wasn't bricked.
Now I have my phone and got the oldest OOS 3.5.1. My changeable Phonename is OnePlus 3T but I got a mail again where it says that I logged in with a OnePlus 3.
I will try to install TWRP and the latest OOS version.
So I finally solved it.
I was a bit confused with the TWRP version, so I thought that I can install the latest OOS with the Oxygen Recovery and I saw, that I used the wrong Recovery for my phone.
I used the right TWRP version for my phone but not the right Oxygen Recovery when I tried it with it.
I thank all you guys for the help.
Fun4Jan said:
So I finally solved it.
I was a bit confused with the TWRP version, so I thought that I can install the latest OOS with the Oxygen Recovery and I saw, that I used the wrong Recovery for my phone.
I used the right TWRP version for my phone but not the right Oxygen Recovery when I tried it with it.
I thank all you guys for the help.
Click to expand...
Click to collapse
No problem, would you mind adding [SOLVED] to the title, so other users with the same or similar problem will read this post to fix their devices too?
Thanks, and happy flashing!
Fun4Jan said:
I tried it with TWRP 3.1.1-2 for the OnePlus 3t
Click to expand...
Click to collapse
Then try with the older version, the newest one is known to cause problems with proper device detection.
Edit: nevermind, just saw it's fixed.

[TOOL][10.0]ONE CLICK TWRP+MAGISK FOR ANDROID Q by Jay's Dev Team.

Jay's Dev Team
Patched Boot Image Flasher for OnePlus 6T!
Another Work made by Jay's Dev Team! No more abandoned support, more frequent updates and tested builds!
Features:
•Android 10 Ports compatible (7T, Pixel 4xl, etc.)
•OOS OpenBeta 1 Q , H2OS BETA 1 Q compatible.
•Pre rooted (Just install Magisk apk)
•TWRP 3.3.1.20 preinstalled
How to Install:
Notes: Backup Your nudes before flashing!
1.Reboot to fastboot
2.Run flasher.bat
3.Enjoy
After it will finish flashing (5-10 seconds), Your phone will automatically reboot into Main OS.
Download:
Patched Boot Image Flasher Android Q Beta 1
NEW
OOS Stable Android 10 Root+Twrp TEST BUILD
Warning! If your device doesn't boot, just use EDL mode or fastboot to go back to stock firmware.
If You have any other problems, just ask here on XDA or for the fastest support ask someone in our Telegram group
Join our group!
Jay's Dev Team:
MounirHero - OnePlus 6T Maintainer & Tester - Donate to Mounir
Jay - OnePlus 6 Main Developer - Donate to Jay
Credits:
@MounirHero for maintaining and testing.
@ProtoDeVNan0 for base OP6 Ports.
erfanoabdi for vendor patcher idea.
Mauronofrio for Twrp.
TopJohnWu for Magisk.
OnePlus for latest firmwares and for creating OP6/6T!
If I forgot anyone, just PM me on Telegram!
​
Thanks !
TWRP work but no decrypt because no format data ?
Heldwin said:
Thanks !
TWRP work but no decrypt because no format data ?
Click to expand...
Click to collapse
Exactly:good:
MounirHero said:
Exactly:good:
Click to expand...
Click to collapse
Perfect ! I do that.
don't update magisk to 20 ?
Nice work dude, I think a lot of people will appreciate this to ease confusion about the whole A10 ordeal for now.
Work perfectly Bro
Thanks for sharing.
UPDATE :
- After flashing it works fine i have TWRP and Magisk for Root but suddenly my sound is not working event when connecting Headset.
Thanks man. !
raidenXXIX said:
Work perfectly Bro
Thanks for sharing.
Click to expand...
Click to collapse
hello no working mac wifi for me.
regards
raidenXXIX said:
Work perfectly Bro
Thanks for sharing.
UPDATE :
- After flashing it works fine i have TWRP and Magisk for Root but suddenly my sound is not working event when connecting Headset.
Click to expand...
Click to collapse
Reinstall the rom through local upgrade to go back to stock
Boot to stock OS and then try again
cultofluna said:
Reinstall the rom through local upgrade to go back to stock
Boot to stock OS and then try again
Click to expand...
Click to collapse
I come from OOS OB 9.0.17 then updated via system update TUT by Sir Funk Wizard then try this to have TWRP + Rooted.
but in end it works perfectly but my sound system fully wipe like my OP6T is in MUTE MODE.
raidenXXIX said:
I come from OOS OB 9.0.17 then updated via system update TUT by Sir Funk Wizard then try this to have TWRP + Rooted.
but in end it works perfectly but my sound system fully wipe like my OP6T is in MUTE MODE.
Click to expand...
Click to collapse
If you flash back the stock boot img sound is working?
Try this...
If sounds are still broken , factory reset...
cultofluna said:
If you flash back the stock boot img sound is working?
Try this...
If sounds are still broken , factory reset...
Click to expand...
Click to collapse
So if i still do this and Still encountering Sound problem i just need to factory reset.
ok i'll try this one, i also see this as a solution about the issue but i don't want my apps to be wipe and install again via backup because it's hassle, that's why i'm trying to get an answer on it without getting a data loss from my current applications installed.
anyways thanks bro for answering my concern. :good:
raidenXXIX said:
So if i still do this and Still encountering Sound problem i just need to factory reset.
ok i'll try this one, i also see this as a solution about the issue but i don't want my apps to be wipe and install again via backup because it's hassle, that's why i'm trying to get an answer on it without getting a data loss from my current applications installed.
anyways thanks bro for answering my concern. :good:
Click to expand...
Click to collapse
You've been moved from Pie to android Q
Its good to make a clean install and start fresh from scratch..
cultofluna said:
You've been moved from Pie to android Q
Its good to make a clean install and start fresh from scratch..
Click to expand...
Click to collapse
If i do this one, maybe i'll try some custom ROM on Android 10 base since i'm starting from the scratch again before settling on my main ROM again
once again Thanks bro
Just need format infernal storage or format all partitions ?
Heldwin said:
Just need format infernal storage or format all partitions ?
Click to expand...
Click to collapse
if you encountering any problem after flashing this on your latest FW, try first to factory reset and check if the issue is still the same.
raidenXXIX said:
if you encountering any problem after flashing this on your latest FW, try first to factory reset and check if the issue is still the same.
Click to expand...
Click to collapse
OK, I can confirm a couple things:
1. With this boot.img I have magisk
2. With this boot.img I have TWRP
But...
I have no MAC ID, so no wifi.
After a complete reset, including formatting data, still no MAC, no wifi
Could this be a difference between the international version and the US version?
michaave said:
OK, I can confirm a couple things:
1. With this boot.img I have magisk
2. With this boot.img I have TWRP
But...
I have no MAC ID, so no wifi.
After a complete reset, including formatting data, still no MAC, no wifi
Could this be a difference between the international version and the US version?
Click to expand...
Click to collapse
I had the same issue with international version.
So will this do all the necessary steps to root my phone and add twrp ? Im still stock and unrooted.
If so, anything i need to do prior ?
Yes, make sure you're on first android Q beta and you have unlocked bootloader.

Battery issue after flashing

Hi folks! I humbly ask for your help after hours and hours of DIY attempts. I rooted a Z5 Compact a few years ago and, mistakenly, expected this to be similar: I didn't read instructions carefully. Admitting to noob mistakes now.
I followed this:
https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
with this option:
https://forum.xda-developers.com/xp...oted-kernel-hiding-bootloader-unlock-t3898711
I went with the G8441_47.1.A.8.49_CE1.rar firmware, as it seems most compatible. THANK YOU j4nn! Marvelous and relatively simple procedure . Flashed with newflasher (Flashtool doesn't work with XZ1 Compact?).
Rooting worked, but when the phone is on battery it never goes above 20%. It was 100% before and 20% immediately after flashing. Red warning light is on, unless the phone is off and plugged in.
So. I missed the part about omitting persist* and Qnovo*. Somehow my attest keys didn't break (PROVISIONED in service test).
It looks like what happened is I replaced the battery config? Info:
https://forum.xda-developers.com/xperia-x/help/flashed-xperia-x-low-battery-t3441158
https://forum.xda-developers.com/xperia-xa/help/strange-battery-issue-jumping-33-3-0-t3688178
Can't repair with Xperia Companion because unlocked bootloader (no way it could be re-locked, is there? My DRM keys are backed up).
Someone wrote about wiping the Qnovo partition. Any advice on how to do this? fastboot format Qnovo didn't work (looks like it doesn't find that partition)
Unrelated, and sorry if this is a total n00b question, but where on earth is TWRP compatible with this device/FW? j4nn's rooted kernel doesn't play well with TWRP install, so I'm hoping to just fastboot boot recovery.img. I can't find any recovery.img that works - I tried several of these:
https://androidfilehost.com/?w=files&flid=232371
But it just gets stuck on SONY logo, needing soft reset.
ben_pcc said:
Hi folks! I humbly ask for your help after hours and hours of DIY attempts. I rooted a Z5 Compact a few years ago and, mistakenly, expected this to be similar: I didn't read instructions carefully. Admitting to noob mistakes now.
Click to expand...
Click to collapse
Try this - https://developer.sony.com/develop/open-devices/get-started/flash-tool and report back.
WORKED. Flashed the US firmware with "Software Update Content Erase", battery now seems to be working normal again. Thank you so much!
Another question: I'd love to set this phone up to work with fastbooting TWRP (so, not a TWRP install on the phone). Is that possible with 47.1.A.8.49? If not, advice on what firmware to use that'll allow rooting per j4nn's methods? Preferably compatible with https://forum.xda-developers.com/xp...oted-kernel-hiding-bootloader-unlock-t3898711
ben_pcc said:
Is that possible with 47.1.A.8.49? If not, advice on what firmware to use that'll allow rooting per j4nn's methods?[/url]
Click to expand...
Click to collapse
Why use such old FW? If you're sticking with Oreo then you want the FW ending .20 for the latest. An unlocked bootloader is all that required to boot TWRP from fastboot on any FW.
Because I didn't know better. Emma gave me 47.1.A.16.20, I'll stick to that
Would you mind sharing what *img file exactly would work with fastboot that way? I had no trouble finding it for the Z5 compact, but one that would work here is eluding me. For example, if I run:
fastboot boot twrp-3.2.3-0-lilac-1.img
The phone boots up to SONY logo (black on white background) and stays there, unresponsive. Got the file from https://androidfilehost.com/?w=files&flid=286271
ben_pcc said:
Would you mind sharing what *img file exactly would work with fastboot that way?
Click to expand...
Click to collapse
Have you missed this post, which is linked to in the threads you've posted links to? - https://forum.xda-developers.com/showpost.php?p=79880858&postcount=1029
I missed it but I also miss how that would help. I read the whole thing, and this stands out: fastboot boot twrp.img
I've done that with my old phone (Z5 Compact). I can't find a usable twrp.img anywhere. I fear like I'm missing something obvious
ben_pcc said:
I missed it but I also miss how that would help. I read the whole thing, and this stands out: fastboot boot twrp.img
I've done that with my old phone (Z5 Compact). I can't find a usable twrp.img anywhere. I fear like I'm missing something obvious
Click to expand...
Click to collapse
From the last page - https://forum.xda-developers.com/showpost.php?p=83844543&postcount=1657
Although I would simply install the latest and use one of the unrooted kernels then root it with Magisk.
Hmm. I was aware of that. I tried several of the twrp*.img files, they all get stuck booting on the SONY logo.
Are you sure this is true:
An unlocked bootloader is all that required to boot TWRP from fastboot on any FW.
Click to expand...
Click to collapse
I'm wondering if a FW update would solve the TWRP booting problem.
I've setup this phone a bit at this point and flashing a new firmware (erasing everything) would be painful. Is there a way to safely do a firmware update on a rooted device? Emma offers 47.2.A.*, but only for UK ROMS. I'd installed the 47.1.A.16.20 US ROM.
ben_pcc said:
Are you sure this is true:
Click to expand...
Click to collapse
I know it used to be. Done a bit more searching for you https://forum.xda-developers.com/search/thread/3706704?query=fastboot twrp, and found this command...
Code:
fastboot reboot bootloader
fastboot boot twrp-3.3.1-0-lilac-pie-5.img
...I've just tried it, in fastboot mode and it booted TWRP.
ben_pcc said:
I've setup this phone a bit at this point and flashing a new firmware (erasing everything) would be painful. Is there a way to safely do a firmware update on a rooted device? Emma offers 47.2.A.*, but only for UK ROMS. I'd installed the 47.1.A.16.20 US ROM.
Click to expand...
Click to collapse
Starting over is always painful but sometimes it's the best option. I have a rooted stock ROM and TWRP installed with no issues, on Oreo or PIE so if you do, then I suggest backing up the essentials and starting again.
YES. Thanks so much SXUsr! You were right after all, I tried a few different TWRP images and they work now. What I was missing was fastboot reboot bootloader. My Z5 Compact doesn't require it.
There was one more thing I had to figure out: data partition is encrypted, and for my (Android 8.0.0) device the TWRP you mentioned fails.
twrp-3.2.3-0-lilac-1.img on the other hand asks for my unlock pattern when it boots up, and backs up fine.
Now that I have a complete backup I'll consider my next steps (possibly flashing a new ROM. Honestly 8.0.0 seems fine, we'll see). Thanks again!!
ben_pcc said:
YES. Thanks so much SXUsr!
Click to expand...
Click to collapse
You're welcome. I've always installed it on this phone so wasn't aware of that command myself either, so we've both learnt something.

Categories

Resources