How to root a Sony xperia Z2 Table - Xperia Z2 Tablet General

I have been trying it for days now , no luck so far.
The Service Code window which is supposed to pop up in the Contacts / Settings doesn't work for me. I've tried to press the screen everywhere for more than 5 seconds. I think mine is one of the model that can't be easily rooted.
I just want to get rid of the default Android and install a vanilla one. Also lineageos would be fine for me.
Things I have been trying :
- lineageos website and related wikis
- sony website to unlock the bootloader
- several youtube guies with no luck
Does anyone have a working step-by-step guide?
Best,
N.

I know this is already one year late, but I hope this answer will help others struggling with the subject.. I did, took awhile to get everything working.
The Sony instructed Contacts app does not work, but the dialer app does the same. Just use it.
LineageOS installation page is a superb reference for help
Install LineageOS on castor | LineageOS Wiki
lineage.harryyoud.co.uk
Sonys own pages are super helfull and give some downloads available:
How to unlock bootloader - Open Devices - Sony Developer World
developer.sony.com
Where I got stuck was trying to get the Fastboot drivers to install on windows 10 since they are not signed Here comes Zadig in play, it will install correct drivers so your computer regognizes the tablet on Fastboot mode
Zadig - USB driver installation made easy
Hope this helps others also

Zadig was the solution!! Thanks a lot!!! Even if there still no working possibility for rooting.

Late to the party, but maybe you want to have a look at this new thread: https://forum.xda-developers.com/t/...xperia-z2-tablet-stock-to-android-11.4356605/
Please also read the thread as there are some useful hints. Just moved my "new" Z2 Tablet from stock Android to LineageOS with root.

Related

Jiayu S3 PIN Locked by Kinguser app

First of all, I may be posting this in the wrong section. But I desperately need your help on this.
I got a Jiayu S3, and couldn't not try to flash a custom rom on it, so I tried with "Pure AOSP V1 TF".
All went well, untill i found this app which was included with the rom, "Kinguser" (should be Superuser, i believe), which game me the option to toggle root.
At first and only time I opened this Kinguser app, option root was active. I did deactivate it, and reactivated immediately after.
As soon as i reactivated root, the privacy pin screen showed up.
I didn't set any PIN on my phone, so at first i thought it could be something like 1111 or 0000. Tried 5 times and it made me wait 30 seconds. Then tried another 3-4 times.
Here began the real mess: "forgot pin" (or psw) didn't show up, but at the time i didn't even know about that recovery option.
I didn't know what to do, so I just thought that a factory reset would certainly solve the problem, how couldn't it? Well, wiped everything, but PIN lock screen didn't go away.
So, wiping everything, I also deleted my gmail account from the phone, and I lost the possibility to lock phone and give it a new password (Android Device Manager). Too bad at the time I didn't know about this recovery option as well...
Now I'm out of ideas. I think I've tried every method I could find with a search of "Smartphone PIN locked". Tried with resets, plugins, deleting files with adb..
How do I unlock my phone?
little update: after a factory reset, for 2-3 seconds, it shows the default initial screen, but it doesn't last more that and i just can't do anything.
Now i managed to bring back the stock rom, but with that i lost the twrp recovery, and i can't find a way to make pc recognize the phone to reflash it.
It seems it's going worse instead of better...
I had just bought this Jiayu S3 and planned to bring it on holidays on wednesday, but i'm starting to think i won't be able to fix it before then
Did you have any resolution to this problem. I am currently sitting in the exact same boat. Did the factory reset, pass code screen still there, I didn't set a pass code. Basically hands tied, can't update firmware, guessing i'll have to get a new phone, but hoping maybe you found a miracle cure! ha! - Thanks for any guidance. - Arden (Seattle, WA)
Just flash another rom (stock/original) and start over.
How have you done that?
Can you help please?
I tried factory reset (volume plus+ power button), hard reset (volume- plus power button), update, and nothing works; I also went to two different specialized stores and they failed to find a way to reinstall the original Android version or a recent one.
Comparing the files with the factory version installed in the phone, the phone report identified three changes:
- a new file: /system/priv-app/7mK0T6e8Z5.apk
- the lost of a file: /system/app/com.android.fallen.apk
- and a modified file: /system/bin/debuggerd
AzulFogo said:
How have you done that?
Can you help please?
Click to expand...
Click to collapse
To flash firmware you can use SP Flash Tool on a windows or linux computer (not sure about macosx). You have to decide which firmware you want (which one do you have now?). The 'official' firmwares can be found on needrom. SP Flash Tool can be found there as well. There are 2 popular LP firmwares built by Jiayu resellers in Europe (Xtreme from Spain and Jiayu.de from Germany). Guides on how to flash are often present at the place where you find the firmware.
Dior DNA said:
To flash firmware you can use SP Flash Tool on a windows or linux computer (not sure about macosx). You have to decide which firmware you want (which one do you have now?). The 'official' firmwares can be found on needrom. SP Flash Tool can be found there as well. There are 2 popular LP firmwares built by Jiayu resellers in Europe (Xtreme from Spain and Jiayu.de from Germany). Guides on how to flash are often present at the place where you find the firmware.
Click to expand...
Click to collapse
Thank you!
I found "Xtreme from Spain":
needrom.com/download/rom-xtreme-rom-tf/
I found the "SP Flash Tool":
needrom.com/download/sp-flash-tool-v5-1424-00/
but it is for Linux... can you send me the link of the windows version?
And I could not found the "Jiayu.de from Germany": can you send the link?
Also, can you recommend some good manual for dummies?
Thanks again for your patient and help!
latest sp flash tools is 5.1532
search needrom with "5.1532" will leed you to the download page
no link allowed here, so ...
for beta 10 from jiyau.de, search google with "jiyau.de Lollipop 5.1.1 - Beta 10 (14.10.2015)".
it will leeds you to the rom.
Good hunting
tuto sp flash tool
https://youtu.be/ztI8sc8MUNo
AzulFogo said:
Thank you!
I found "Xtreme from Spain":
needrom.com/download/rom-xtreme-rom-tf/
I found the "SP Flash Tool":
needrom.com/download/sp-flash-tool-v5-1424-00/
but it is for Linux... can you send me the link of the windows version?
And I could not found the "Jiayu.de from Germany": can you send the link?
Also, can you recommend some good manual for dummies?
Thanks again for your patient and help!
Click to expand...
Click to collapse
see jaunedoeuf's answers
I would like to add: if you come from KK and go to LP, you must use firmware upgrade to update/adjust internal SD partition layout. Good Luck! if you succeed, and are happy with firmware, consider voting @ http://forum.xda-developers.com/android/general/firmware-jiayu-s3-t3212184 (almost 100 votes)
First, thank you for your great help!
With your suggestions, I managed to install Lolipop in my Jiayu S3S (upgraded from Kit Kat) - Xtreme ROM TF (JiayuS3-5.1Extreme1.1SP.zip).
However the problem remain... the phone still is asking for a PIN (that I never had put there, in first place)...
What should I do now?
you could try factory reset and are you sure its the phone asking for pin and not the sim card

[XIAOMI REDMI NOTE 3 PRO] Guide to Unlocking,common MiFlash and MIUnlock solutions.

Hello folks, this is my first ever post on XDA forums and I want to share how i bricked my Kenzo and the errors that i came across before unofficially unlocking my device. And also the solutions .
So firstly, some info
1. Kenzo doesnt have a recovery from the start.
2. As I read, Kenzo requires you to be on developer version of rom for unlocking bootloader the official way.
3. Xiaomi Servers are really bad, so say you want to unlock your device and you got your permission granted then its not clear when xiaomi will update that into their servers. I kept getting the 86012 error which as per forums is due to Xiaomi not updating the device info in their servers.
4. The unofficial way is much faster and imo better as it doesnt require you to wait like 10 days or so to get your permission granted with the only demerit that it would go away the moment you install a new MIUI rom. But you can reunlock it using the same method so no worries.
Oh and btw, do the disable driver signature enforcement for your windows before doing anything . https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Also, make sure your battery is >80% . Ik its quite common to do this but in my case my battery was 50% and after flashing multiple times it was 0% and i got the red led so i thought i was booting into edl mode but after putting it to charge i realized that it was the low battery indication .
Now , guides and fixes.
1. So to unlock the device officially you need to headover to the site mentioned in your miui, and to get to that firstly enable developer options then go to developer options>mi unlock state and in the bottom is the link and follow the steps. I suggest waiting 24 hrs after getting the permission granted (which usually takes 5 mins) and then trying to add acc using the button in mi unlock state.
2. If you get the 86012 error, you are in the same boat as most of the people so the only way to officially unlock the device now is to wait 2-30 days.
3. If you get the couldnt connect to network error, download the developer version of your rom and follow instructions to install it. And then try.
4. Now, if you got your permission granted and the add acc thing worked then Congrats . Now if you download the Miunlock app and get the "Account doesnt exist" or "Network Error" error then switch the internet connection, in my case ,if i used vodafone mobile data hotspot then i got the error but with airtel no error. And after getting this Miunlock completed successfully your bootloader is unlocked.
5. Now the unofficial way, simple thing . Follow this https://forum.xda-developers.com/redmi-note-3/how-to/guide-rn3-pro-se-t3565172 .
6. There are 2 types of edl mode on kenzo, first is when you get 900E in device manager, second is when you get 9008 in device manager on your pc. For any flash to work, you need to get 9008 .
7. Now most likely you might run into "Object instance " error or something like that or even "max buffer size 250k" using Miflash app to install a fastboot rom on kenzo. The fix is to firstly install the 2014 version of miflash app and then after running it on your pc and finding your device using it install latest version and run that. The preferred location to install the app is in C:\ instead of C:\Program Files. Also I used the 2016 version downloaded from a website rather than the latest official one .
8. Your device may get bricked and might only boot to edl mode and the 900E mode at that. To get into 9008 mode, either use edl cable or do the test point method .
9. For custom roms you dont need a modified boot.img which I was unable to retrieve for myself anyway. You can create them too.
Thats all i can gather for now, I will add more issues if i discover more and I hope that I get help from the mods and admins on the forums regarding putting reserved messages and all so that everyone who has a fix and reports here can benefit everyone else
I didnt include much links cause there are quite a few of these guides and I only wanted this to be a support thread and not a full guide .

Noob looking for pointers to help with upgrade process

Hi. Been waiting a while to post this, and playing around based on what I see, but I the last change I made to my phone hasn't worked out too well and I don't think I have enough of a grip on the process. I am an ex-computer 3rd level tech support so I have reasonable skills around computers etc.
I bought an Axon 7 (A2017G) in Germany but it got flooded one day when it went down the toilet pan, literally. So I replaced it with a 128 Gb model from China, not really thinking about the software versions. Of course it came with A2017, and more importantly, no ability got OTA upgrades from Android 6.
So recently I've been having some battery life issues so I've changed the battery.
Following guides here, I've managed to get it onto a newer A2017 version and it has taken an OTA upgrade to Android 7. The build number is B13. The boot loader is still unlocked. But it's not very stable and Google Play service has now stopped, and I can't be doing with the unreliability. And tbh although it worked, I can't remember exactly which guide or what steps I followed to do it.
So I want to put it onto a stock G version, which I think seems to be possible, based on stuff I've read here. I don't think I need root going forwards (once this is done) and I'm looking for the simplest method. Unfortunately, due to the length of time it's been live, this forum really is information-overload and I've been reading for two days now and made loads of notes but I'm not really very clear about what I need to do.
I'm quite happy to find and read the right guides but would be really grateful if someone could take a few minutes to just tell me exactly which bits are essential to be upgraded and what steps I do need to follow. If I am confused I can come back with any queries.
I'd be happy to root the phone if it's felt that is a really useful thing but I'm not really a "power user" and I'm OK with standard.
Also I'm assuming any upgrade would receive any future Android releases OTA (if there are any for this phone), but if not that's not too vital.
Thanks in advance...
Geoff
But regarding your situation: You have an A2017 with A2017G firmware, right? Can you tell us your firmware version?
Would you be fine with Chinese firmware (MiFavor 5.2, B17) or prefer stock+ (G B01/B02, U B12)?
Thanks for the quick response, really appreciated.
The firmware is still A2017 version AFAIK, but I don't know where to check. If I go to the boot loader screen it says ZTE/P996A03_N/ailsa_ii and on the next line 7.1.1/NMF26V/20170912.013327
I'm thinking I'd do the change from A2017 to A2017G to get round the annoying junk which came with the Chinese version, and also avoid the Google Play Services problem I came across. It may not be do-able but I thought I'd read it was.
I guess in addition to telling me the steps, telling me exactly which file versions to use would help a lot. I promise to keep notes!
I don't mind which firmware, so long as it works reliably and so long as I can preferably put a G version on it.
of course it's doable, the thing is that you'll need to unlock the bootloader in order to.
If you had trouble with Play Services then it's most probably on chinese firmware, finding out would be as easy as going to Settings, then About phone
The boot loader is still unlocked from when I managed to do the previous upgrade. That took me quite some hours, and it was more by luck than judgement that I got a result. This time I want to better understand what I'm doing.
Not sure what I'm looking at for the firmware, isn't it the versions I quoted above? But the menus (mostly) are in Chinese at start up, and I had to load Google Play and Play Services from the ZTEYR store so I'm pretty sure it is on Chinese firmware.
So if it is, do I just need to upgrade the firmware then the ROM (is that the terminology?). If so which versions would I use?
Ta
Geoff
EDIT I missed the kernel version - which is 3.18.31
OK so I've spent more time reading. I'm coming to the conclusion that I don't need TWRP and I don't need to update my Chinese bootloader, does that sound about right?
Is it right that all I need to do is
- find a G firmware zip file <<< may have incorrect terminology here, would appreciate a pointer to a valid download as I have many but not sure they are the right type of file
- put it on an SD card named as update.zip
- boot into recovery mode
- choose "apply update from SD card"
And, assuming I have used a stock version, will it then update to the latest version (hopefully Oreo) once it's started?
Do I need to do any formats or wipes anywhere in the process? I already have a backup of my stuff, done with AXON7Toolkit.
And can you recommend a version of firmware to go to, or does it not really matter as it'll update itself anyway?
UPDATE: MiFavor UI is v5.0
OK, so there is no real short easy answer to this.
I've used the updates from ZTE since I've had the phone until I soft bricked it.
Zte offer updates similar to this.
Eg: B06 to B08 or B08 to B09 and B09 to B12
The update has to be done in stages.
Some updates you can copy to the internal SD card then go settings > system > update, your phone should detect the updates and tap install.
Some Zip files can be done the same way after changing the file name to update.zip or Ota.zip depending on the instructions.
Some zip files have the update within the Zip so it needs to be extracted.
Make sure you have the correct version software and correct version for your phone.
After the update is done all the data etc will be still in place unless you reset your phone.
All I can say is research, research, research.
Btw if your bootloader is unlocked some updates will fail.
I hope this helps
PS: you can use the method you described as well, just follow the instructions carefully.
In most cases there is no need to wipe or format unless you are using a custom ROM etc.
Excellent, thanks.
Going back a post or two - I re-installed Google Play services but still have problems. Before a reboot it appears in the list of apps, and Play opens, but the sidebar comes straight in and behind there is a message "Error while retrieving information from server [RH-01]" . After a reboot it is no longer in the list of Apps (even when expanded to include System apps), and Play just opens and closes real quick.
So I found a thread which led me look in Settings in Play Store at the Play Protect Certification, which says the device is not certified. So I downloaded the related app and ran it, which gave me a code which I put in web page then entered the stuff into my phone but still no joy. I suspect this is causing the Play problem and I think it'd be due to trying to use Google product on a Chinese firmware (again I'm not sure my terminology is right - I mean whatever the software is which throws up the initial boot screen).
So I think I need to get off the Chinese firmware at the same time as going to a G version, and I'm even less clear on how to replace the firmware than the rest of the process - what files and how it's done.
Going back to the more recent post (Syberclone), as I have already wiped my phone I'm not concerned about keeping data. I understand about doing this is steps - I hadn't thought of doing it that way but it seems very sensible.
I found a post by Raystef66 with loads of links to software - including A2017X_B15_Universal_Bootloader.zip. Does this replace the Chinese firmware and would it work with all zipfiles? How would I apply it? (I was using Axon7ToolKit the other day and that looks quite impressive).
I am still confused over the different types of files and the naming conventions but it's slowly making more sense. Appreciate all advice.
Thanks
Geoff
Personally I use Edl packages much easier imo.
I use Miflash or Edl tool by @djkuz
I have a bad flash help page that explains the process.
The bootstacks etc are mainly for custom ROMs, if you are just looking a factory firmware, Edl's are much easier to install without worrying about bootstacks, twrp etc.
My last Edl update was from Nougat (Chinese Rom)
To Oreo A2017G I had to factory reset after the install though.
Thatnks. Today I've done a fwe more hours reading, literally. This is taking all my time!!
Anyway I decided to follow your advice and found a full EDL of Oreo, which I applied. (ZTE_A2017V3.0.0B17) and the phone is still working, and I've not lost my apps.
However I still have the problem that Play Services won't run. I've upgraded it, followed a few troubleshooting guides, used different versions ( - should I be using the 64 bit one??) but still no joy. If I could only get that going I'd stick with the Chinese firmware. It is looking to me like it can't sync, though whether that's a cause or an outcome I'm not sure. Not unexpectedly, a number of apps will not run as a result.
I haven't done a factory reset yet, I thought I'd ask here first to see if that is likely to fix it or whether anyone has any better ideas.
Despite the time this is taking I'm enjoying learning and am grateful to you all for the responses.
The play store link "device not certified" will happen when you change a ROM from its original.
So I have an A2017G, when I run any other ROM it will show "device not certified" because the link between the phone and the software isnt in sync.
When I was running the beta Oreo from the Chinese my device always had this issue and NFC does not either usually.
There is a play store app version which will work as it should however the certified is still a problem without a work around.
When I installed the G version Oreo to my device the certification is back.
I'm miss some of the Chinese ROM animations tho.
Anyway I hope this helps
I am using an A2017 ROM on an A2017. I've not changed anything else. Maybe I need to update the boot stuff (firmware?).
What I'm seeing is that Play Services always needs to be manually enabled, and seems to drop out and require re-installation sometimes. So I have an apk on my internal memory for quick access.
I'm not sure that the "device not certified" is a cause or effect really.
So I have an apk on my internal memory for quick access. It's the latest non-beta 64bit version for Android 8 - should I try a specific one, e.g. is there likely to be a specific one which matches the ROM? (An older non 64 bit one seemed to give much the same problem)
I'd put up with the problem except I can't run some Google stuff at all (Play Store for instance), and some other stuff is compromised (e.g. I can't get into Waze on my usual ID, I'm guessing Play Services plays a part in authorizing). And I can't install some stuff I'd like.
And I'd still be interested to know which bits require upgrade to go to a G version, if it is do-able and would run trouble free.
There was a play store app that worked on most ROMs.
You are on Oreo now yes?
There was a link on one of the Android pie ROMs that I used, it worked fine.
If you are still having issues you can use an app called Yalp that works like the play store.
I've used it on custom ROMs when the play store app refuses to work.
Yes, Oreo now.
I've put YALP on and that looks pretty good. I now seem to have most things working, and those that aren't I can probably live without.
I use a network tool called FING which reports my phone details, and I think it's incorrect but it's saying in one place it's a A2017U which I don't think is right. But now I am more comfortable with EDL and stuff I'm going to continue to fix this properly but the urgency is now not there. I was thinking if I couldn't fix this I might have to buy a new phone on black Friday!! So thanks for your help.
I'm still not really quite sure why I get Chinese characters at start up and what files I need to change to out a G firmware on, if that is what is wrong, and if it's do-able. I think if I knew how to do that then I could put on a G firmware and matching ROM and I'd be in business!!
The same page offered me F-DROID which seems to offer a whole load of different free apps. Maybe they don't have ads? Anyway I'll have a look.
Anyway, again - thanks!!
Geoff
Geoff I'm glad I could help
I was running the Chinese Oreo on my phone and after selecting English in setting some parts of the ROM were still in Chinese, even some notifications.
I converted to the A2017G Oreo update when it was released.
I miss some of the features in the Chinese ROM tho.
So... without wishing to prolong this... your phone was Chinese (as mine was) and you are now running a Global version and all you upgraded was the ROM? And are you able to use the Play Store and you don't have any issues running apps I - and can you run, say, Google Maps?). Is your bootloader still unlocked and if so is the menu at boot time still in Chinese?
Or have you upgraded something other than the ROM?
I actually have an Axon 7 A2017G here in Australia.
I soft bricked it when I accidentally made a mistake flashing a ROM.
I searched for a suitable stock firmware but I could only flash the Chinese Oreo Beta. It had to be modified to run on my device until the Oreo package for my A2017G had been uploaded.
I've now running the proper software for this phone.
Thanks.
Another couple of hours and I have made a Major breakthrough! I went back over all my notes and checked what i'd done and one thing I hadn't remembered doing was setting the Pay Store to Autorun. So using the Mi-Assistant I have done this, and most of the stuff which wasn't working now is. I am still working on why OK Google won't work, but the list of things I might have to live without is now quite short!! The one major benefit is that my battery life seems to be greatly increased. Boot time is also much quicker which is a bonus but not critical.
Nice, yes battery life is improved, actually the Chinese Oreo Beta has a better battery life than my current Oreo.
I could get up to 4 days out of the Chinese ROM, my current ROM can manage just over 3 days at best.
I have battery saver mode on but not ultra battery saver.
I hope this has been a good learning experience for you?
"I hope this has been a good learning experience for you?"
For sure it has. Back in the days when I was 3rd level computer techie, the best learning came from other experts and from being thrown in the deep end, rather than what they taught you in the classroom!

XT1572 updating from nothing

Hi.
This might be a very noobish question, but these cannot be avoided from a noob who pretty much avoided smartphones until now:
Can someone explain to me how I get a never used EU clark up to date?
Apperently the former owner had it sitting in a drawer since *ever*, so it is still on Android 5.1.1 (systemversion reports 23.21.18.clarkreteu though, which sound like a resonable recent date to me). The phone claims to have the newest software installed and support was no help either, but apparently there were once OTA updates at least to 7.0 and even that is barely sufficient for many apps nowadays. (Not that I intend to use many apps, as I dislike the Google play store)
I searched several days in vain for some form of guide, but every single one i found expected at least an 6.0.x bootloader and most unofficial=new OS even start out with Nougat installed. But how can I get there? (Or, if it is resonable easy, directly to some current LineageOS or whatever you recommend.)
ruyven_macaran said:
Hi.
This might be a very noobish question, but these cannot be avoided from a noob who pretty much avoided smartphones until now:
Can someone explain to me how I get a never used EU clark up to date?
Apperently the former owner had it sitting in a drawer since *ever*, so it is still on Android 5.1.1 (systemversion reports 23.21.18.clarkreteu though, which sound like a resonable recent date to me). The phone claims to have the newest software installed and support was no help either, but apparently there were once OTA updates at least to 7.0 and even that is barely sufficient for many apps nowadays. (Not that I intend to use many apps, as I dislike the Google play store)
I searched several days in vain for some form of guide, but every single one i found expected at least an 6.0.x bootloader and most unofficial=new OS even start out with Nougat installed. But how can I get there? (Or, if it is resonable easy, directly to some current LineageOS or whatever you recommend.)
Click to expand...
Click to collapse
The easiest way to update stock is LMSA.
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Hi & both thanks for your quick reply & sorry for not coming back earlier. But LMSA proved very troublesome, promting me to delay my experiments until easter. Results after a quite some additional hours (restart, reboots, reinstalls, various methods of access, trying each and every menu on phone and in LMSA,...) however remains zero.
No matter how I do access the rescue option, after selecting my phone (auto detect only works in "my device"), come only the "wait for matching software" prompt and than, a grey, semi transparend overlay. On the first dozen or so tries I thought LMSA crashed completely (causing me to run extensive tests of my PC before retries...), because it remains visible but does not response to any clicks. Now I noticed that I can still access the window itself via task manager, only mouse clicks are captured by said overlay. I guess some rescue process is supposed to start, but it simply does not for me.
(Alternative) Suggestions?
ruyven_macaran said:
Hi & both thanks for your quick reply & sorry for not coming back earlier. But LMSA proved very troublesome, promting me to delay my experiments until easter. Results after a quite some additional hours (restart, reboots, reinstalls, various methods of access, trying each and every menu on phone and in LMSA,...) however remains zero.
No matter how I do access the rescue option, after selecting my phone (auto detect only works in "my device"), come only the "wait for matching software" prompt and than, a grey, semi transparend overlay. On the first dozen or so tries I thought LMSA crashed completely (causing me to run extensive tests of my PC before retries...), because it remains visible but does not response to any clicks. Now I noticed that I can still access the window itself via task manager, only mouse clicks are captured by said overlay. I guess some rescue process is supposed to start, but it simply does not for me.
(Alternative) Suggestions?
Click to expand...
Click to collapse
With LMSA try starting the phone in bootloader ap fastboot mode, then connect to PC, then start LMSA, select rescue.
Looks like this is the last update for Clark RetEU
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
RETEU/XT1572_CLARK_RETEU_7.0_NPHS25.200-15-8_cid7_subsidy-DEFAULT_CFC.xml.zip
The next best option is RSD Lite, but this only works with older Window 7 or Xp PCs
If you don't have an older PC use fastboot.exe or mfastboot.exe
download the firmware from the lolinet link, unzip the file, find flashfile.xml, open with a text editor like notepad, copy text and paste at online flashfile convertor, to get flash commands.
Links in
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Older PCs are speciality of mine.
RDS worked perfectly and I am on 7.0 now. Thanks a lot.

Help Needed - Pixel 4 - No WiFi+Data after update

Hello everyone. I recently purchased a used Pixel 4. Past owner said WiFi+Data stopped working after updating Android and that the phone is unlocked and carrier-free. I need to unlock bootloader in order to install GrapheneOS but it is greyed out. As you can see in the screenshots, it seems like the phone is not recognizing WiFi and IMEI hardware while booted. IMEI does show up in the barcode menu option in fastboot. System UI crashes if I try to open WiFi config. The only thing I could try was tethering via Bluetooth from my other phone and updating Android OS and apps. Already tried wiping everything and forcing phone to connect to Google while on Bluetooth tethering by pressing (*#*#2432546#*#*) in the dialer as sugested here: https://source.android.com/setup/contribute/flash#preparing-your-device
This doesn't show any success or error message.
One thing that may have happened is this: https://www.phonearena.com/news/google-pixel-android-12-verizon-update-issue_id136367
Apparently Google sent OTA Verizon update to unlocked Pixel 4's by mistake. Maybe the wrong software is what is making it not recognize WiFi+Data?
Current installed build is 12.1.0 (SQ3A.220605.009.A1, Jun 2022). Maybe I should wait for a new SP* instead of SQ* build to come out and try installing it? This is because P is for the main platform branch as explained here: https://source.android.com/setup/start/build-numbers#build-ids-defined
Hopefully it comes out before October since that is the end-of-support date.
OTA builds: https://developers.google.com/android/ota#flame
Other option would be to try out this but it seems the riskiest and last resort option:
Unlock carrier locked bootloader Pixel [BETA]
UPDATE AS OF 16 OF MAY 2023 This project isn't working right now, but I am still working on it. However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get...
forum.xda-developers.com
And yet another option would be to purchase a new board and replace it.
What do you think? I tried submiting the IMEI to T-Mobile's site and it says it is OK to be ported. Verizon's site didn't let me submit the IMEI I don't know why. And for AT&T I didn't find any site for that. IMEI checks say it is not blacklisted.
Did u solve this?

Categories

Resources