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.
Related
I already opened an RMA for the phone but they have no stock so I figured I'll take another shot at it.
The short version is that my gf messed up and updated the system while transferring her data from her old phone with the tapNgo thing.
I've done multiple facory resets, downloaded the rom from ZTE support, put it on SD, flashed it from recovery and deleted cache and nothing helps.
I don't have the exact error log anymore since I don't have the phone with me now but it reads something along the lines of
loading /proc/devices/audio/sound------ cannot find file/directory.
I looked it up and after a lot of Googling it seems like the symlink to the actual driver folder is missing and I have no idea why.
Does anyone know if i can fix this with an ADB shell?
Alternatively, I tried to follow some of the many guides out there to put the phone in EDL mode and relfash it with XiamiFlash utility but after trying 3-4 downloads and 900 versions of misflash all I ever get is "reading hello packet... unable to communicate to com4"
Haaaalp please?
*edit* this is pretty much exactly the same as what I'm getting: https://forum.xda-developers.com/android/help/sound-card-detected-t3379736
The problem with the phone is it makes no sounds?
gpz1100 said:
The problem with the phone is it makes no sounds?
Click to expand...
Click to collapse
the sound drivers for the OS is missing completely, no sound no microphone.
The syslog looks like this(this is from another phone its its the exact same problem):
AudioDaemon: Opening sound card state : /proc/asound/card---/state
AudioDaemon: Open /proc/asound/card---/state failed : No such file or directory
AudioDaemon: Sleeping for 100 ms
Strange issue indeed. Which model do you have? Which specific firmware file are you flashing to it?
I would think flashing the full unmodified factory firmware using the stock recovery will wipe the phone completely, including the /data partition.
Everything worked before? Help me understand the order of events. What is tapngo?
While in the midst of transferring information to or from the phone, a software update appeared and she accepted/installed it?
Its the A2017U model.
I had tried the 1.1.0 B15 firmware from SD card as well as the 1.0.0 B29 older firmware.
Right now its on B17 Nougat 7.1.1, the phone runs and works perfectly just has no audio hardware.
I wasn't there for the exact procedure but basically she powered it on, it asked for sim, she inserted that, tapped the "transfer my data" and then held the two phones together to get the NFC process started. That starts the bluetooth transfer process and it takes a really long time where it transfers all data and apps from the old phone.
At this point the phone still made sounds when adjusting the volume etc.
Somewhere in that process the "update available" notification came up and she pressed the option to install it.
After I got home I tried to figure out what is wrong, first i thought the phone wasn't registered on the cellphone network but then after a bit i figured out the audio is the issue, then i did a factory reset both from the phone UI and tried again from recovery mode, both times chose the "erase all data" option but neither time did it help at all.
I don't really know enough about phones but i think its the bootloader/something very early on thats messed up. Either that or the audio chip really just did fry.
My hope was to get the full factory image for everything that you need to install with the EDL mode thing but I can't find any good reliable guides for that.
It's the first thread in the development section.. Stickied even.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Get this package - B15-NEW_FULL (Nougat)
I really don't understand zte's numbering scheme. Newer versions get lower numbers. Makes no sense. That's the full firmware except for the fastboot which passes commands. At this point it's a non issue given the issue you're having.
So I don't need to load TWRP on it, I can still keep it just stock with unlocked bootloader?
I tried that miflash thing before, i had it connected un usb download mode but nothing worked for me, I'll try doing this guide when i get home step by step again.
Their firmware numbers is based on numbers and letters 1.0a-z and then 1.1a-z so 1.0z1 is less that 1.1a1
Ok I have an update
Did miflash, nothing changed.
Ulocked bootloader and miflashed the bootloader from the sticky thread.
The phone made the startup sound and audio worked for a few seconds after android started up and then stopped again
*edit*
ok so after it showed signs of life i re-locked the bootloader, and did the OTA updates to 7.1.1 and the audio seems to be working for good now!!
Conclusion seems to be the bootloader was the key to get it working again. Hope this helps others if it comes to it.
Hello experts!
First off I do admit I have cross posted some information here. Perhaps I should have just asked here first. As a lot of research I have been doing lead me here. I am also aware of the XY problem. So I am giving what information I have on my problem and what I have done to resolve it. In a nutshell I need to recover app data from internal storage.
So here is yet another story of a dropped Samsung Galaxy BSOD. The broken screen of death! :-o
So I dropped my phone and the screen broke, fixed it then put on a screen protector that fractured the new screen in my pocket, of all things. Through that it spiraled out and it needed a new LCD as well as screen which failed to repair as LCD remains blank now. I suspect the display controller has somehow fried. Decided to give up and buy a new phone.
My broken phone is a Core Prime G360G. The digitizer doesn't respond. The LCD is blank. The side buttons, volume, power and home, work fine.
The good news. It turns on and technically still works. It has no screen lock. I can plug it in to computer via USB and it mounts over MTP. I can also install apps remotely (so to speak) from another computer from the Play site. I've installed Samsung Switch this way. Switch does work and I managed to back up files from the Windows program which is good but in my case it isn't smart enough as it doesn't back up app data which I need. I also have AirDroid installed and can reach it that way I but didn't enable mirroring before the incident. Trying to use that to download an app (~10MB in my case) just results in the browser stalling.
The bad news. It is not rooted. It has stock standard firmware. USB debugging is not enabled. Last time I tested OTG wasn't supported. At least not for OTG USB sticks.
So in effect it's rooted without being rooted! Yes, i know, I know, Android rule of thumb; before you accidentally drop your phone, even without planning it, and not being a seer, enable USB debugging for no apparent reason! It all makes sense now.
I've spent the last two weeks reading forums all over the place, blogs and watching videos about how to recover data with a broken screen. And in almost all cases they tell you to enable USB debugging. Well that's nice advice and about as useful as advising someone with a broken toilet to sit down, do their business and then flush it! And is met with equally crappy commentary pointing the conundrum out.
My computer has Windows (Vista) and Linux (Mint 64). I read all about ADB and installed this on both Windows and Linux. And tried to talk to it that way with adb and fastboot which failed. I then read of Samsung devices being different, with a download mode, and using this Odin or Heimdall program. So I could "see" the process I tested with my new phone (a J5 Prime as it happens) and learned I needed to use download mode and how to enter it on boot. Recovery mode didn't work as expected. Heimdall was the only program that would work. I managed to view the PIT on my J5. Odin did see my phone but I found the interface harder to work with at first.
I tried on my Core. Blindly got it into download mode. Heimdall could see it. But the transport was buggy as I kept getting USB errors. I ended up removing it then compiling Heimdall v1.4.2 from source. This worked better, even though it was giving empty bulk transfer warnings, but it managed to download the PIT file. So at this point I can blindly get my Core into download mode and am able to communicate with it using Heimdall.
This is where I am at. I would prefer it if a screen mirroring app could be installed that would load up and activate remotely when a client run on my computer is loaded up. I don't care if it is VNC or how it connects. But it would need to load itself up on the phone and work without needing intervention on the phone and without USB debugging. If there is an emergency mirroring app on the Play store or even an APK that can be installed remotely, using AirDroid or any other means, I would be happy to test it. I'd write one myself if knew how to write an app! LOL.
If USB debugging could be enabled by any remote means then I am welcome to hear how. It opens a window to possibility. But a window that is hard to open if it's locked.
So I would prefer to keep this at the app level if possible. Since apps can help. But if need be as long as it doesn't destroy data I am willing to install a custom recovery image. It looks like I will need to do this as I have exhausted all other possibilities. At least, when I read of the latest broken screen mirroring app, there is always a catch of it needing debugging or activating on the phone.
Although there is support for other Core Prime variants, support for my specific G360G model seems to be lacking. The information I read looks vague at best. I read about CWM and TWRP. But on the TWRP site, although there is Core Prime images, nothing is listed for exactly a G360G. There is no point to me flashing TWRP recover image only to find it doesn't work and I have bricked recovery mode. I'd look like a right twerp!
So guys, after all the info I have given you, what's the next step? Thanks.
Okay so just an update here. I have some good news and bad news on my part. I've been hacking around with customising recovery and modifying compatible recovery images in order to get debugging activated.
The good news is I got USB debugging enabled. The bad news is my computer is unauthorised.
I'm stuck at this point. I updated the adb_keys file with what was on my computer and it won't budge. I finally get somewhere and now I've once again hit a wall. This is just so annoying. :-x
The final countdown. After months of cracking and hacking I've broken in! I modded my hack to create the needed folder just to be sure and updated my RSA key. Applied the firmware patch and let it reboot. Even while booting I knew something was different. The digitizer started responding to my touch and making water noises. Which was strange as I never noticed it doing that before.
I issued an adb command and it was accepted. I could then browse around the system. I already had screen mirroring software installed and all it needed was USB debugging working and suddenly it worked. This was a blessing as I found that trying to do other things like going into a root shell or do an adb backup caused a requester to come up on screen. Had I not been able to satisfy that on a virtual screen I would have run into the same trap of circles I had just climbed out of. Having a rooted phone with no root access.
I was then able to install a backup app and extract the data out. Hooray! I had actually installed it from Google Play site remotely but found there was no space for it and it had failed. But the account said it was installed. With a view to a mobile I could then remove another app and install it from Play on the phone itself. Given how well this worked once I learned what was needed to be done I suppose I should make up a guide. An automated script to create an ADB patch wouldn't go far astray.
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!
Hi everyone.
I just recently got a used S5e, mostly for the Dex capability. I am a consultant, so sometimes I'm in a location where I need a desktop, but don't always have room for my 15" laptop. I haven't had a Samsung device in years... preferring brands with easy root and a nearly limited skinning (currently, OnePlus devices... basically).
I had kind of resigned myself to not having root on this device, since it is a Samsung, so I was surprised when I came on here to see if anyone else was having the update problem, I found root threads. Currently, my device looks like it's on the May 2019 update (One UI 1.1, Android 9, Build PPR1.180610.011.T720XXU1ASED).
Still trying to resist rooting the device, especially since I saw the no-root debloat thread. But I would like to know how to get this stupid thing updated. From what I've read, it has to do with an XML file containing a Samsung URL that returns a 404 when queried manually. The software updater doesn't reflect that, though... and just says you're up-to-date.
So if I can root this and flash a debloated ROM, that would serve a few purposes. Otherwise, if there's a way to force an OTA (or find it and download it to the SD card), that would be fine, too.
Any advice.
Flapjack said:
Hi everyone.
I just recently got a used S5e, mostly for the Dex capability. I am a consultant, so sometimes I'm in a location where I need a desktop, but don't always have room for my 15" laptop. I haven't had a Samsung device in years... preferring brands with easy root and a nearly limited skinning (currently, OnePlus devices... basically).
I had kind of resigned myself to not having root on this device, since it is a Samsung, so I was surprised when I came on here to see if anyone else was having the update problem, I found root threads. Currently, my device looks like it's on the May 2019 update (One UI 1.1, Android 9, Build PPR1.180610.011.T720XXU1ASED).
Still trying to resist rooting the device, especially since I saw the no-root debloat thread. But I would like to know how to get this stupid thing updated. From what I've read, it has to do with an XML file containing a Samsung URL that returns a 404 when queried manually. The software updater doesn't reflect that, though... and just says you're up-to-date.
So if I can root this and flash a debloated ROM, that would serve a few purposes. Otherwise, if there's a way to force an OTA (or find it and download it to the SD card), that would be fine, too.
Any advice.
Click to expand...
Click to collapse
If I'm understanding you right, you just want an OTA update applied? If that's the case, Frija is what you want to get the latest firmware for your device, and Odin will be your flasher. For stock rom flashes you don't even need an unlocked bootloader, much less root!
There are a ton of guides for Odin available, but still, if you have any questions please post!
Thanks for the reply!
I've used Odin quite a bit in the past, but I do know different situations need different files, so I'll probably do a quick refresher.
As for root, it definitely is a nice-to-have, mostly to remove bloatware, but if the debloat thread here works pretty good (and someone has info on just how much I can remove and keep Dex functionality), I would love to know that as well.
So, I am having a new problem. Using Frija, I downloaded the latest update. However, no matter what I do, I can't get a PC to recognize the tablet in download mode. It just says something about Windows not being able to recognize the device. In Device Manager, it says: "Device descriptor request failed". I've tried with and without the Samsung drivers, with three different USB cables, on two different PCs.
I'm worried that something is physically wrong with the USB port. That doesn't really make sense, though... as it charges fine, and shows up in Windows correctly once it's fully booted to Android.
**EDIT**
False alarm. I needed to press "up" again after getting into download mode and connecting the PC. So odd. It's updating now!
Hey! This is my first time here, sorry if I'm doing smth wrong, I just really need help. My fossil gen 6 is kinda useless at this point after updating to Wear OS 3 and I would like to flash it back to Wear OS 2, since I don't get any notifications & I can't even sync my notes at this point without connecting to wifi (not even through mobile data, which is pretty annoying -> my phone & watch doesn't connect to each other through bluetooth)
thanks, for any guides in advance!
night
You will have to perform a factory reset and repair the watch and phone again. Only option at the moment.
edwin270 said:
You will have to perform a factory reset and repair the watch and phone again. Only option at the moment.
Click to expand...
Click to collapse
Did that 3 times already, nothing changed. Thanks for your answer though!
Did you get anywhere with this? I also want to go back to wear os 2. I hate the fossil app
I'd like to know too. I just came back to Android with the S23 Ultra and wanted to pair my Razer x Fossil watch to it. But I decided to update since I was doing a factory reset/disconnect anyways. Big big BIG mistake.
There has to be a way to flash wear OS 2.3 back to the watch and re partition it as stock. I'm able to see my watch as a USB perhp on my machine without BT or wifi connection.
Anyone have the old firmware for these watches? Short of buying another Razer watch for $600
I do have all the required files to go back to wearOS 2, but wont suggest it might brick your device. Have a partition backup first.
For OTA add the hash in the placeholder.
Main URL: https://redirector.gvt1.com/packages/data/ota-api/package/<hash_with_extension_here>
v2.30: 230d380c72f87f94cbd4e43b944afd70700d6ffd.zip (Apply updates from playstore regarding wearOS to get it upto 2.38)
Minor Update: 4e201fee66e76ed4694e77eaa589f7767f93beea needs to applied after flashing the above package.
V3: a569fe07dfdcb4edea85f9535d592b9af4621cd1.zip
Malvik said:
I do have all the required files to go back to wearOS 2, but wont suggest it might brick your device. Have a partition backup first.
For OTA add the hash in the placeholder.
Main URL: https://redirector.gvt1.com/packages/data/ota-api/package/<hash_with_extension_here>
v2.30: 230d380c72f87f94cbd4e43b944afd70700d6ffd.zip (Apply updates from playstore regarding wearOS to get it upto 2.38)
Minor Update: 4e201fee66e76ed4694e77eaa589f7767f93beea needs to applied after flashing the above package.
V3: a569fe07dfdcb4edea85f9535d592b9af4621cd1.zip
Click to expand...
Click to collapse
Hey ! Thanks for the file. I'll take the risk to brick my watch.
Do you know how I can flash the archive ?
MiamKebab said:
Hey ! Thanks for the file. I'll take the risk to brick my watch.
Do you know how I can flash the archive ?
Click to expand...
Click to collapse
I'm also looking to be able to flash my watch between WearOS 2 and 3. Have you figured anything out by chance? All the things I normally do aren't working, with and without TWRP.
Malvik said:
I do have all the required files to go back to wearOS 2, but wont suggest it might brick your device. Have a partition backup first.
For OTA add the hash in the placeholder.
Main URL: https://redirector.gvt1.com/packages/data/ota-api/package/<hash_with_extension_here>
v2.30: 230d380c72f87f94cbd4e43b944afd70700d6ffd.zip (Apply updates from playstore regarding wearOS to get it upto 2.38)
Minor Update: 4e201fee66e76ed4694e77eaa589f7767f93beea needs to applied after flashing the above package.
V3: a569fe07dfdcb4edea85f9535d592b9af4621cd1.zip
Click to expand...
Click to collapse
Or would you be able to provide some guidance on how to proceed?
Arkbird1000 said:
I'm also looking to be able to flash my watch between WearOS 2 and 3. Have you figured anything out by chance? All the things I normally do aren't working, with and without TWRP.
Click to expand...
Click to collapse
From what I found, the original cable with 4 spins (2 on each side) should be used to connect your watch to a PC and use the USB debugging.
So I bought one but nothing happened. I'm just able to use Bluetooth or WiFi debugging and these can't be used to unlock the bootloader as WiFi and Bluetooth are disabled on bootloader mode. So fastboot can't detect the watch.
So I'm stuck and that sucks, my duck.
Another way is to remove the watch's back and tweak the USB connectors but I'll not do that...
MiamKebab said:
From what I found, the original cable with 4 spins (2 on each side) should be used to connect your watch to a PC and use the USB debugging.
So I bought one but nothing happened. I'm just able to use Bluetooth or WiFi debugging and these can't be used to unlock the bootloader as WiFi and Bluetooth are disabled on bootloader mode. So fastboot can't detect the watch.
So I'm stuck and that sucks, my duck.
Another way is to remove the watch's back and tweak the USB connectors but I'll not do that...
Click to expand...
Click to collapse
I see. I have been able to make it farther, but I also was running into problems getting the USB connection to work. Most of what I did was under Linux instead of Windows but I found that after enabling USB debugging I often had to remove the watch from the cradle, put it back on, then run 'adb devices' from the connected computer to get the daemon going. That usually got the adb popup on the watch to show, then I can select the 'always allow' option.
All that said, at the moment I'm not currently able to boot my watch unless I have the bootloader unlocked. I have restored the stock recovery after using TWRP and unsuccessfully flashing anything via that adb shell or from the bootloader with fastboot. Even worse, some things are not working properly, such as automatic brightness and some of the wireless capabilities. I might need to see if I can work something out with Fossil if I'm unable to resolve these issues.
You guys seems way ahead on me in the downgrade process...
I made Wear OS 3 update but the Fossil app used to pair the watch won't work with Oneplus 8 Pro (Android 13), gotta go back but i have no idea how...
Yet i flashed a lot of custom roms and stuff in the past, but now.. kinda lost
Im looking forward to see news here
Good luck guys, i'll keep updated if i somehow manage to flash the OTA posted ahead
Edit : well i was on Apkmirror to try an older apk of the app, and found out their app targets android 12 but not android 13..........
Arkbird1000 said:
I see. I have been able to make it farther, but I also was running into problems getting the USB connection to work. Most of what I did was under Linux instead of Windows but I found that after enabling USB debugging I often had to remove the watch from the cradle, put it back on, then run 'adb devices' from the connected computer to get the daemon going. That usually got the adb popup on the watch to show, then I can select the 'always allow' option.
All that said, at the moment I'm not currently able to boot my watch unless I have the bootloader unlocked. I have restored the stock recovery after using TWRP and unsuccessfully flashing anything via that adb shell or from the bootloader with fastboot. Even worse, some things are not working properly, such as automatic brightness and some of the wireless capabilities. I might need to see if I can work something out with Fossil if I'm unable to resolve these issues.
Click to expand...
Click to collapse
I do have the TWRP but need to find it, took some tweaks from Ticwatch 3 pro. I didnt pushed it on the repo tho. I didnt what made me do it, but I wiped my system partitions and had to rebuilt from the OTA only. But after getting the watch working again, I had few functionalities broke, including the OTA updates. If you can social enginner your way thru fossil to get files such as stock rom and other files for qualcomm software like rawprogrammer and firehose files it can be great help.