Related
The IMG is made for Moto X 2nd Gen sold in China mainland aka " XT1085" which was released a week ago. Major retailers in China have started to sell since Feb 5.
I can confirm the system also works well on my XT1095 pure edition,however Moto engineers have removed almost all of the google apps and services and implemented some key features with native chinese apps,like Moto Voice. Most of the bloatwares can be easily removed except a security app of lenovo and a voice assistant named Linxi.
You can get the full IMG from a mirror server in china or file factory
Mega
md5sum: 95306D8D80B1F60285E14D2A6FD7F4F0
XT1095 pure edition users can flash the boot.img and system.img via Fastboot utility.(1.Please backup your data before doing this!
2. Just flash the boot.IMG and all system image chunk files. Don't flash other partitions especially GPT and Bootloader,otherwise you would upgrade BL to 0x6012.)
As the Google apps, we can find many flashable zips in the forum,like @TKruzze's PA Gapps packages.
This work in xt1097? And how about root?
xarcom said:
This work in xt1097? And how about root?
Click to expand...
Click to collapse
It should work since there is almost no big difference in android system between 1095 and 1097. However, you should unlock BL first.
As the ROOT, chainfire's CF-Auto-ROOT image still works or you can flash TWRP recovery to your device via fastboot, and flash the root binaries from within TWRP.
I downloaded but how install? Sorry i'm noob , i have unlock bl
xarcom said:
I downloaded but how install? Sorry i'm noob , i have unlock bl
Click to expand...
Click to collapse
0.Backup your personal data.
1.Unzip the image.
2.Put your phone in AP fastboot mode.
3.fastboot flash boot boot.img
4.fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk. 3
5.fastboot -w
6.fastboot reboot
Does the Moto Voice works in other languages? Also the system is all in Chinese or we can change it to English or in my case Spanish.? Thanks.
Auto reply
Nop, the moto voice is not working with any language besides chinese, what I did was to uninstall via Titanium the moto voice, reboot and install the normal apk and everything is great now
No google stuff so battery life must be better than the stock rom we use
About 5.0.2, maybe a fix for the memory leak bug is included?
alexfiorani said:
No google stuff so battery life must be better than the stock rom we use
About 5.0.2, maybe a fix for the memory leak bug is included?
Click to expand...
Click to collapse
5.0.1 has fixed the memory leak bug.
purejoy said:
5.0.1 has fixed the memory leak bug.
Click to expand...
Click to collapse
Memory bug is still present
And Google knows about it
They are set to fix it in 5.1.
I noticed the same thing. Memory leak bug still present, though things did seem better (maybe placebo). Eventually background apps started closing out on me as often happens when using stock 5.0.
---------- Post added at 01:02 AM ---------- Previous post was at 12:48 AM ----------
@purejoy I'm curious how you knew flagging this to our pure edition phones was safe. Someone just posted images for 5.0.2 on US Cellular, and I was thinking of giving it a try. Thoughts?
http://forum.xda-developers.com/showthread.php?t=3032735
mercado79 said:
I noticed the same thing. Memory leak bug still present, though things did seem better (maybe placebo). Eventually background apps started closing out on me as often happens when using stock 5.0.
---------- Post added at 01:02 AM ---------- Previous post was at 12:48 AM ----------
@purejoy I'm curious how you knew flagging this to our pure edition phones was safe. Someone just posted images for 5.0.2 on US Cellular, and I was thinking of giving it a try. Thoughts?
http://forum.xda-developers.com/showthread.php?t=3032735
Click to expand...
Click to collapse
The hardware architecture is almost the same except communication modules and many 1095 users in China have been testing it since the IMG was released.
As the 1093's firmware, we can just flash the kernel and system partitions. The android system should work.
purejoy said:
The hardware architecture is almost the same except communication modules and many 1095 users in China have been testing it since the IMG was released.
As the 1093's firmware, we can just flash the kernel and system partitions. The android system should work.
Click to expand...
Click to collapse
After I flash this version, I cannot go back to the official 5.0 because i think the firmware is not good at all. When I trying to restore it to the original one, I found that I cannot boot. I've tried every firmware that I can find for XT1095.
zhangyang_haha said:
After I flash this version, I cannot go back to the official 5.0 because i think the firmware is not good at all. When I trying to restore it to the original one, I found that I cannot boot. I've tried every firmware that I can find for XT1095.
Click to expand...
Click to collapse
check if the system is flashing good, sometimes the fastboot commands says system ok, but your phone will prompt a message error
juliospinoza said:
check if the system is flashing good, sometimes the fastboot commands says system ok, but your phone will prompt a message error
Click to expand...
Click to collapse
each time i flash, it says that the image is too large. I tried different times but it doesnt work
zhangyang_haha said:
each time i flash, it says that the image is too large. I tried different times but it doesnt work
Click to expand...
Click to collapse
Same is happening to me, I dont know if is my computer or something, but one question, when you are trying to flash the new version are you flashing all the files or only the system.img? because In my case the (partial) solution was to flash motoboot.img, wich is the bootloader version, and then all the other files... I said partial because I am in one ROM I dont want. Maybe later at home will check with other PC, this is 8.1 and the one at home is 7.
juliospinoza said:
Same is happening to me, I dont know if is my computer or something, but one question, when you are trying to flash the new version are you flashing all the files or only the system.img? because In my case the (partial) solution was to flash motoboot.img, wich is the bootloader version, and then all the other files... I said partial because I am in one ROM I dont want. Maybe later at home will check with other PC, this is 8.1 and the one at home is 7.
Click to expand...
Click to collapse
OK, I've found the problem. We can never flash back to the official 5.0 again because Motorola update the bootloader in the chinese version. It is impossible to downgrade the bootloader version. It happened the same thing when I used Milestone 2.
zhangyang_haha said:
OK, I've found the problem. We can never flash back to the official 5.0 again because Motorola update the bootloader in the chinese version. It is impossible to downgrade the bootloader version. It happened the same thing when I used Milestone 2.
Click to expand...
Click to collapse
Flashing back to the original is no problem. Flash all files except for the bootloader and you'll be fine.
zhangyang_haha said:
OK, I've found the problem. We can never flash back to the official 5.0 again because Motorola update the bootloader in the chinese version. It is impossible to downgrade the bootloader version. It happened the same thing when I used Milestone 2.
Click to expand...
Click to collapse
we have to wait till some 5.0.2 version is released, in the meanwhile the OP should warn all the users about upgrading the bootloader
thanks
Steve-x said:
Flashing back to the original is no problem. Flash all files except for the bootloader and you'll be fine.
Click to expand...
Click to collapse
except for the boot loader? Do you mean that motoboot.img?
zhangyang_haha said:
except for the boot loader? Do you mean that motoboot.img?
Click to expand...
Click to collapse
Don't flash the bootloader partition otherwise you would upgrade BL to 0x6012. Just flash the boot.IMG and all system image chunks.
For people looking for the latest YP2 firmware release: Today Yota officially released the 1.87 firmware. It's still Lollipop 5.0, and Russian region only at the time of writing. It should however be pretty usable for e.g. EU too if you're eager, english UI language is included in the RU ROM too). I haven't tried this firmware yet, but I intend to.
If you're currently on RU firmware, check for a FOTA update (about phone->system updates).
If you're on another region firmware and are patient, just wait till it shows up as a FOTA update anytime soon.
If you're on another region firmware and a bit less patient and a bit more daring, you can download RU1.1.87 here, and flash it with yotaflasher. Backup first, own risk etc.
Thanks!
YotaReader's been beautiful! :good:
Have successfully updated to 1.87 and then booted twrp recovery to flash superSU. Can confirm root is successful and the updated room works well in the UK
MAX_G said:
Have successfully updated to 1.87 and then booted twrp recovery to flash superSU. Can confirm root is successful and the updated room works well in the UK
Click to expand...
Click to collapse
Any noticeable improvements...?
Ta
Battery life now stems fine with yota energy showing five days per charge, there are some new yota apps and double click features on the screens, even android auto now works
Is German also as UI language available?
MAX_G said:
Have successfully updated to 1.87 and then booted twrp recovery to flash superSU. Can confirm root is successful and the updated room works well in the UK
Click to expand...
Click to collapse
Did you get an OTA or flash the rom from twrp?
First I loaded the usb ADB drivers then unlocked the Bootloader from the command line after that I used yotaflasher tool to load the new ROM that I downloaded from their website and then sideloaded the TWRP recovery partition to help flash the superuser zip.
I'm wondering how to update using yotaflasher exactly and where to put my downloaded file? because when i tried that my phone just got stuck on Android logo, I fixed that but I want to know and understand what i did wrong
you need to move the firmware files to the same location as the Flasher tool
Mine is C:\Program Files (x86)\yotaphone_flasher ( your directory may be different )
if you got stuck on android it could be a bad download or it could be just doing the update.
IIRC mine was stuck on android initially but after a rebbot it started updating all the android apk files and then booted and ran fine.
Max
All up and running and all good.
I can confirm the procedure is the same as the last one (for those having used Yotaflasher. I hadn't but it's pretty straightforward).
Backup > unroot > flash stock recovery > yotaflasher (with firmware in right directory) > boot > flash su > ....... > profit!
Thanks again SteadyQuad
MAX_G said:
you need to move the firmware files to the same location as the Flasher tool
Mine is C:\Program Files (x86)\yotaphone_flasher ( your directory may be different )
if you got stuck on android it could be a bad download or it could be just doing the update.
IIRC mine was stuck on android initially but after a rebbot it started updating all the android apk files and then booted and ran fine.
Max
Click to expand...
Click to collapse
I personally didn't have to unlock or root the phone. I just downloaded yotaflasher and looked on the net for the right usb drivers. Then downloaded the rom with yotaflasher (4.4.3 EU) and flashed it. Didn't have any issue with file download or location it cause Yotaflasher did everything for me. After reboot it started to upgrade and now I am downloading via OTA 1.60 EU. Think will stop with it , waiting for the next EU rom. Will report in the next days any bug if I find.
Cheers
PS: Max I looked at your signature and saw that you own G. Glass too, if I am not wrong. Maybe I will ask you a couple of questions if you do not mind in the future cause mine went crazy in the last period and cannot understand what is the problem. Anyway I will try to read a bit over the net before bothering you. Cheers
Seem that 1.87a EU has been made available on Yota official ftp site. Anyone has tried it yet? I checked OTA update with the 1.60 EU installed, but as for now, I do not see any update available. Just would prefer not to use yotaflasher , cause I prefer OTA due to the fact it seems to me safer
lexman941 said:
Seem that 1.87a EU has been made available on Yota official ftp site. Anyone has tried it yet? I checked OTA update with the 1.60 EU installed, but as for now, I do not see any update available. Just would prefer not to use yotaflasher , cause I prefer OTA due to the fact it seems to me safer
Click to expand...
Click to collapse
Just got EU 1.87 OTA Update!!! Installing now!!
Rarelyamson said:
Just got EU 1.87 OTA Update!!! Installing now!!
Click to expand...
Click to collapse
Just got the update as well - attached some screenshots!
Looks like the russian firmware are now another few versions ahead ;-( ftp://fw.ydevices.com/YotaPhone2/Firmwares/RU/
irl_x10_user said:
Just got the update as well - attached some screenshots!
Looks like the russian firmware are now another few versions ahead ;-( ftp://fw.ydevices.com/YotaPhone2/Firmwares/RU/
Click to expand...
Click to collapse
Like the double tap to wake, although not sure how my pocket will handle it!?
Hopefully it will also improve my battery!
Hello,
I'm having big problems flashing any ROM on my Oneplus 5 atm.
At the beginning of this month, I wanted to unroot my rooted Android 8.0 or 8.1 (One of them, it was OxygenOS, but not the newest version)+ Xposed Oneplus 5.
I got a couple of errors, most of the time error 7.
After hours, old and new recoverys (TWRP) from blu_spark, codeworkx and some xda user recoverys and diffrent OxygenOS versions i finally managed it to install a Oxygen version with Android 7.1.1 on the phone. The Problem was: I always got errors (Installation failed) when I wanted to intall Software Updates no matter if I tryed it by myself or with the official system update in android.
So and today the official beta build of OxygenOS for 9.0 released and I was so stupid and thought I can make this an easy one.
Now I'm sitting here since 9:30am and try to flash Android 9, or any Android except 7.1.1 (only Oxygen Versions). Most of the Time i'm getting ERROR:7, it doesnt matter with which Recovery or Build.
When I got this problem at the first Time, my Phone was shown as "" (The error was something like: This Package is for a "Oneplus 5" this is a "").
When I get this scentence now (not every Recovery is showing it) it says my Phone is a "OnePlus5T", but i have a Oneplus 5.
Also (maybe partly) important things are:
- I tryed to edit the updater-script and delete the assets lines but there were no asset lines. Tryed it anyways and it didnt work. (and i really dont want to try this again)
I tryed to google this error for hours and many people meant that this is the way to go but I dont belive it. Isn't there any way to rename my phone, if yes: what do I have to do? I have TWRP and access to the command prompt aswell. If anyone can successfully create the 9.0 beta without the assets I would be happy but i dont think that is the solution for my problem, just a workaround.
- I think the problem is just something about my devices name. The strange part is that it accepted 7.1.1. And this was 100% a Oneplus 5 ROM.
- 7.1.1 isnt the way to go for me anymore. I dont like android 7 and it has so old security patches..
- Fingerprint sensor and screen got replaced
thank you for reading this and maybe helping me. I dont have the best language skills, if you need more Information about my Phone, please ask
EDIT1: As I said, 7.1.1 is still successfull, i tryed it a couple of mins ago. no error 7 or sth
maybe you can try revert to fully stock setup{without TWRP) and update to pie?
I have problem with error 7 when i tried to flash latest open beta (pie). I didn't find any solution.... :crying:
petryrety said:
I have problem with error 7 when i tried to flash latest open beta (pie). I didn't find any solution.... :crying:
Click to expand...
Click to collapse
Make sure the download isn't corrupt or if you extract the compatibility.zip use a recommended tool.
I had this problem couple of months ago. I solved it by flashing an old os version then flashing stock recovery(I don't remember if I locked the bootloader). boot in to the phone and download and update through ota( I did 3 updates this way). Then install twrp and root. Now I can flash any oos update without error 7.
May work
This is a post I wrote for another thread. I have found that this method fixes the error 7 issue, and allows you to update all the way to Pie without issues. When updating to Pie, use 7-Zip, not winrar or any other non-recommended programs to remove compatibility.zip from the firmware archive before flashing. I found that winrar causes treble errors or error 7.
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
iwantademo123 said:
This is a post I wrote for another thread. I have found that this method fixes the error 7 issue, and allows you to update all the way to Pie without issues. When updating to Pie, use 7-Zip, not winrar or any other non-recommended programs to remove compatibility.zip from the firmware archive before flashing. I found that winrar causes treble errors or error 7.
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
Click to expand...
Click to collapse
Yeah, that's what I wrote here https://forum.xda-developers.com/oneplus-5/help/massive-problems-error7-t3878372/post78503983 and in flashing instructions for open beta and stable builds in their first posts.
strongst said:
Yeah, that's what I wrote here https://forum.xda-developers.com/oneplus-5/help/massive-problems-error7-t3878372/post78503983 and in flashing instructions for open beta and stable builds in their first posts.
Click to expand...
Click to collapse
That's good, It's good advice. I am just stressing to everyone in this thread, how important it is to follow that and use a recommended tool to remove compatibility.zip because removing compatibility.zip sounds very trivial thing, but it's actually really important to use a tool like 7-Zip that doesn't break the firmware in the process.
Also, the link to my other post ( https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13 ) should be detailed and comprehensive enough to help people with error 7 in other scenarios or that are trying to update to oreo or other stock firmwares too. This method restores the phone back to factory condition, including all the partitioning. Updating with a locked bootloader can fix a lot of update errors. I've found that after 5.1.5 it is safe to unlock the bootloader and take updates. But as you mentioned, for an unlocked bootloader, compatibility.zip needs to be removed from the firmware archive, and a tool such as 7-Zip must be used to do so as other archive managers break the update entirely (with error 7).
Good luck everyone trying to update, hope our advice helps :good:
So I flashed OOS 5.0.1 then went back to stock recovery. I then locked my bootloader. After which I booted into OxygenOS and updated it all the way to pie(took 3 OTAs). Now I've got a locked bootloader and pie but I'm wondering if the process to unlock the bootloader is the same or different now that there is a vendor drive?
TurtleSandals said:
So I flashed OOS 5.0.1 then went back to stock recovery. I then locked my bootloader. After which I booted into OxygenOS and updated it all the way to pie(took 3 OTAs). Now I've got a locked bootloader and pie but I'm wondering if the process to unlock the bootloader is the same or different now that there is a vendor drive?
Click to expand...
Click to collapse
The unlocking process of the bootloader is the same!
I am having the exact same problem, tried everything from above. Can get anything more recent than 7.1.1 on my oneplus 5. evrything else is error 7. Any update
mathgerm said:
I am having the exact same problem, tried everything from above. Can get anything more recent than 7.1.1 on my oneplus 5. evrything else is error 7. Any update
Click to expand...
Click to collapse
Please see here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post79938097
Hi,
Two weeks ago I unlocked and rooted my mi a1 (which was running android pie v10.0.3.0.) with magisk. When I saw the January update was released, I wanted to unroot the phone and I uninstalled magisk. However, the phone rebooted and there was only “no command” screen.
Now I wanted to flash the stock rom to save my phone by flashing the stock rom again, but as you may know, Xiaomi hasn’t released the official android pie firmware on its website. And I can’t go back to Oreo firmware due to anti rollback protection.
I found several v10.0.3.0 firmwares on the internet and downloaded them. However this time I’m having trouble while flashing the stock rom via Mi Flash Tool. When I wanted to flash the firmware, Mi Flash Tools gave error “can not found file flash_all_lock.bat” or any other bats. When I checked the firmware files, there were _Flash_lock.bat, _Flash_.bat, _Flash_erase_userdata_lock.bat and _Flash_erase_userdata_lock.bat files.
Any ideas how I can sort this problem out? Any immediate assistance will be much appreciated.
Thanks
finxminx said:
Hi,
Two weeks ago I unlocked and rooted my mi a1 (which was running android pie v10.0.3.0.) with magisk. When I saw the January update was released, I wanted to unroot the phone and I uninstalled magisk. However, the phone rebooted and there was only “no command” screen.
Now I wanted to flash the stock rom to save my phone by flashing the stock rom again, but as you may know, Xiaomi hasn’t released the official android pie firmware on its website. And I can’t go back to Oreo firmware due to anti rollback protection.
I found several v10.0.3.0 firmwares on the internet and downloaded them. However this time I’m having trouble while flashing the stock rom via Mi Flash Tool. When I wanted to flash the firmware, Mi Flash Tools gave error “can not found file flash_all_lock.bat” or any other bats. When I checked the firmware files, there were “_Flash_lock.bat”, “_Flash_.bat”, “_Flash_erase_userdata_lock.bat” and “_Flash_erase_userdata_lock.bat” files.
Any ideas how I can sort this problem out? Any immediate assistance will be much appreciated.
Thanks
Click to expand...
Click to collapse
what about deleting those underscores before each word, i think they shouldn't be there.
kuartito said:
what about deleting those underscores before each word, i think they shouldn't be there.
Click to expand...
Click to collapse
I tried but no success. Maybe I'm doing wrong to use mi flash tool. Maybe I should just try to use bat files through fastboot, I don't know. I haven't found any information on the forum or google if I can do it like that.
finxminx said:
I tried but no success. Maybe I'm doing wrong to use mi flash tool. Maybe I should just try to use bat files through fastboot, I don't know. I haven't found any information on the forum or google if I can do it like that.
Click to expand...
Click to collapse
i'm by no means an expert and my advice has no value at all, but i don't see why you wouldn't give flashing from fastboot a try.
1: Those firmware are not meant for miflash, flash using twrp
2: Don't use the script that locks if you wanna avoid trouble.
What directory did you select in miflash?
JakobSWE said:
1: Those firmware are not meant for miflash, flash using twrp
2: Don't use the script that locks if you wanna avoid trouble.
Click to expand...
Click to collapse
I downloaded 3 copies of 10.0.3.0 firmware from different places and each one claimed those firmwares were for fastboot, not twrp. I attached the folder's screenshot.
henk_j said:
What directory did you select in miflash?
Click to expand...
Click to collapse
I attached the screenshot of the directory.
finxminx said:
Hi,
Two weeks ago I unlocked and rooted my mi a1 (which was running android pie v10.0.3.0.) with magisk. When I saw the January update was released, I wanted to unroot the phone and I uninstalled magisk. However, the phone rebooted and there was only “no command” screen.
Now I wanted to flash the stock rom to save my phone by flashing the stock rom again, but as you may know, Xiaomi hasn’t released the official android pie firmware on its website. And I can’t go back to Oreo firmware due to anti rollback protection.
I found several v10.0.3.0 firmwares on the internet and downloaded them. However this time I’m having trouble while flashing the stock rom via Mi Flash Tool. When I wanted to flash the firmware, Mi Flash Tools gave error “can not found file flash_all_lock.bat” or any other bats. When I checked the firmware files, there were _Flash_lock.bat, _Flash_.bat, _Flash_erase_userdata_lock.bat and _Flash_erase_userdata_lock.bat files.
Any ideas how I can sort this problem out? Any immediate assistance will be much appreciated.
Thanks
Click to expand...
Click to collapse
flash this official pie rom
http://bigota.d.miui.com/V10.0.4.0....0.PDHMIXM_20190104.0000.00_9.0_2cee840c96.tgz
...
Stuck in Loading Screen after Update Magisk
I have the same problem here,, This morning i got nontification from Magisk to update to the new version,, and update done, Magisk start reboot,,, when reboot,, i always stuck on Loading Screen. I check from TWRP my Internal Storage cannot detect by Pc,, So i think i cannot doing Flashing by TWRP,, I'm wipe out all data to clear this mess,, so i start to do a flashing with MIFlash, i'm download the custom rom and start flashing.. and i got this message "cannot found file flash_all_lock.bat"
Sorry for my Bad english.. cus i'm still young
Hi,
Lost root access after updating my OnePlus 6T to Android 11 a few days back, hence decided to flash magisk_patched image that I had created around 2 months back. Phone didn't like it ofcourse and gave me a QualComm Crash Dump error.
After searching, managed to boot into bootloader, however wondering how do I now boot my phone - I have downloaded and installed latest recovery (3.5.2_9.0-fajita.img) and am able to boot into recovery as well as bootloader/ fastboot.
Have also downloaded the zip file for Android 11 stable version - OnePlus6TOxygen_34.J.60_OTA_0600_all_2108052232_8c516d0cce8795.zip
Question - What do I need to flash this? adb commands don't seem to be working, only fastboot commands seem to. Can I just "push" this zip file in fastboot or is that only for img files?
Any help woud be massively appreciated!
The update to 11 does not agree with Magisk which causes it to either fail to complete the update or to die at early boot depending on how bad things were messed up. You can reapply root once the update to 11 is finished though, so you can still have root.
In your case manually upgrading to 11, letting it finish the upgrade, and then installing Magisk again is your best bet, in which case you would either have to find something that understands the update format or manually extract the updated partitions from the payload, iirc
Extracted boot.img and used fastboot command : fastboot boot boot.img, but this doesn't seem to have worked as well. Just thinking aloud what else can be done?
Edit - It now tries to boot, but then seems to go into OnePlus Recovery (from the chinese characters displayed along with an option to choose English language)
sam_htc_touch said:
Have also downloaded the zip file for Android 11 stable version - OnePlus6TOxygen_34.J.60_OTA_0600_all_2108052232_8c516d0cce8795.zip
Question - What do I need to flash this? adb commands don't seem to be working, only fastboot commands seem to. Can I just "push" this zip file in fastboot or is that only for img files?
Click to expand...
Click to collapse
Masamune3210 said:
The update to 11 does not agree with Magisk which causes it to either fail to complete the update or to die at early boot depending on how bad things were messed up. You can reapply root once the update to 11 is finished though, so you can still have root.
In your case manually upgrading to 11, letting it finish the upgrade, and then installing Magisk again is your best bet, in which case you would either have to find something that understands the update format or manually extract the updated partitions from the payload, iirc
Click to expand...
Click to collapse
Hi, thanks for responding. I am not even concerned about root right now, just want my phone to boot up first Any suggestions on what can I try?
sam_htc_touch said:
Hi, thanks for responding. I am not even concerned about root right now, just want my phone to boot up first Any suggestions on what can I try?
Click to expand...
Click to collapse
For the benefit of others, all sorted finally y'day evening. Plenty of helpful tips in this thread
(Well I was able to boot into Android 11.1.1.1 - no root as yet, but I will perhaps look into that later, can't stand those annoying ads :-D )