Hi!
I received J8110 from Sony as a service exchange unit (they could not repair my other model). It came originally with Android 9 1317-9334_55.0.A.2.205 GLOBAL-A1. I have not unlocked it.
It never got any OTA update for this over 2 years old firmware, so I decided to flash it myself using flashtool. As I could not find exactly matching 1317-9334 on XperiCheck, I used 1318-3803 Android 10 "Internal Service Exchange Unit 55.1.A.9.127-R1B" firmware. It did flash correctly, and almost everything works - except both Netflix and HBO Max reboot the phone whenever I try to play any video. Moreover, the phone reboots itself randomly once a few hours, and I must say it is really irritating issue.
The last entries in Android logcat just before reboot look like this:
Code:
03-07 10:18:41.251 886 17948 D WVCdm : [license.cpp(355):PrepareKeyRequest] PrepareKeyRequest: nonce=3174971344
03-07 10:18:41.313 886 6842 I WVCdm : [cdm_engine.cpp(191):CloseSession] CdmEngine::CloseSession: sid10
I suspect it might be somehow related to Widevine keys. But the DRM info app shows everything is OK and L1 support is enabled (as in the attached screenshot).
I tried to flash also other firmware images - everything available for J8110 in XperiCheck (including 55.2.A.4.332), but the phone won't boot - "Your device is corrupt. It can't be trusted and will not boot.". I even tried flashing J8170, but that eneded up even worse, in recovery: "cannot load Android system". This 55.1.A.9.127-R1B (that reboots my phone on Netflix) is the only firmware I was able to boot.
My first question: is there any way to downgrade to this original, obsolete but working Android 9 1317-9334_55.0.A.2.205 GLOBAL-A1? I can't find it in XperiFirm.
And, of course - if you could point me on how to install the more recent Android versions that work I would be very grateful. I would prefer to leave the phone locked as I suspect some DRM issues with unlocking, but if that is the only way and it is confirmed working I can try it as well.
Service menu *#*#7378423#*#* "software info" of original and updated firmware attached.
Thanks for any help!
I forgot to mention that of course I tried clearing data and cache for Netflix app, as well as uninstalling and re-installing updates (can't fully uninstall the app as it was included in the firmware). I could fully reinstall HBO though, but fresh install did not help with the issue at all.
Did you tried the Firmware with version 205 on XperiFirm?
There is one called SA or ZA.
Get things into your PC and use newflasher by @munjeni. It will work if there is nothing wrong with hardware.
Thanks for the response.
I have tried the newflasher as well, but the results are exactly the same as for flashtool - "Your device is corrupt..." (or recovery error, depending on firmware). I don't think this is an issue with flashing itself, I did not notice any error in logs.
Yes, I have tried this 205 "Customized ZA" also - it does not boot, stops in recovery "Can't load Android system". I did not try to factory reset the data yet, as I really would prefer to keep my user data intact.
I have tried every single firmware available in XperiCheck for J8110, and only this 1318-3803 boots for me - but reboots my phone every hour or so and this is really annoying.
I have also asked XperiCheck maintainer to add my 1317-9334, but no response so far.
Plz provide the frimware that is working in your mobile i am facing the same problem my device stuck on sony logo i will be thankful to you brother
Related
Heya. Since I haven't updated phone for quite some time now (I'm still at 2.0.49), so is it safe to upload to latest version, via SE PC Companion, to still have root access, for xrecovery, flashing etc.. That's question number one.
Question number two would be - if phone, x10i keeps random restarting, mostly while browsing websites via stock browser (usually, screen just "freezes" for few seconds (6-8 at most), and phone just reboots, showing that SE boot logo). If it's software related - would update, that I mentioned above fix that, if not... Phone is still under warranty (at least I hope ).
Yes, Update definitely. That should fix your software related problems.
And I'll still be able to root it, and flash ?
yes you will still be able to root, just download latest flasher, plug your phone and root it, optimize, install xrec and many more
Hello,
I've bought a new device - Evolveo StronPhone Q4, MTK6589 based phone. The stock ROM is basically vanilla Android 4.2.1. I've successfully rooted it using Framaroot.
Then I've created scatter file using MTK Droid Tools (all partitions that were formated were ext4).
Then I've decided to create a backup before I start playing with it, so I've tried backing up flash using SP Flash Tool (using Readback), it was running fine and downloaded approx. 20%, then crashed. I've tried that once or twice more times, always failed. Now after I plug it in, windows display "This device can perform faster" and FlashTool won't detect the device. If I connect it without battery with VolDn key pressed, FlashTool detects it and I get S_DL_GET_DRAM_SETTING_FAIL.
However, the phone boots fine, just GPS/Wifi/BT is not working. (No GPS icon appers, and I get errors like BT_open: WMT turn on BT fail in dmesg). Looks like an issue with kernel/HW issue.
Any ideas what could have gone wrong and how to fix it?
In the meantime, I've asked manufacturer for a stock FW image, but I'm not sure it helps...
Update: Okay, I have no clue what just happened. However I've unrooted, reverted everything I've modified on the phone so far so I'll be able to return it to manufacturer as "deffective"... And just for the curiosity connected it to the computer and tried downloading ROM one more time. And it succeeded - I'll upload the ROM once I get access to faster internet connection. I've removed the battery (phone was stuck in Preloader mode because I cancelled ongoing RAM test.), put it back and now everything works.
So, it looks like everything is fine now, however I'd love to know what happened, if you have any clue, please let me know!
fw problem
Mrkvak said:
Hello,
I've bought a new device - Evolveo StronPhone Q4, MTK6589 based phone. The stock ROM is basically vanilla Android 4.2.1. I've successfully rooted it using Framaroot.
Then I've created scatter file using MTK Droid Tools (all partitions that were formated were ext4).
Then I've decided to create a backup before I start playing with it, so I've tried backing up flash using SP Flash Tool (using Readback), it was running fine and downloaded approx. 20%, then crashed. I've tried that once or twice more times, always failed. Now after I plug it in, windows display "This device can perform faster" and FlashTool won't detect the device. If I connect it without battery with VolDn key pressed, FlashTool detects it and I get S_DL_GET_DRAM_SETTING_FAIL.
However, the phone boots fine, just GPS/Wifi/BT is not working. (No GPS icon appers, and I get errors like BT_open: WMT turn on BT fail in dmesg). Looks like an issue with kernel/HW issue.
Any ideas what could have gone wrong and how to fix it?
In the meantime, I've asked manufacturer for a stock FW image, but I'm not sure it helps...
Update: Okay, I have no clue what just happened. However I've unrooted, reverted everything I've modified on the phone so far so I'll be able to return it to manufacturer as "deffective"... And just for the curiosity connected it to the computer and tried downloading ROM one more time. And it succeeded - I'll upload the ROM once I get access to faster internet connection. I've removed the battery (phone was stuck in Preloader mode because I cancelled ongoing RAM test.), put it back and now everything works.
So, it looks like everything is fine now, however I'd love to know what happened, if you have any clue, please let me know!
Click to expand...
Click to collapse
hello,
could you please upload somewhere original fw for Evolveo Strongphone Q4. im in bootloop now
Hi all,
can you hel me with strongphone Q4, do you know any better rom for this phone?
Maybe by PM in czech? ...
I registered my account on this website just to share my awesome experience with Nokia 1.
I am very much thankful to XDA and many other sites whose text assisted me in recovering my mobile.
WARNING: VERY LARGE TEXT BELOW AND ITS JUST MY EXPERIENCE, I AM NOT RESPONSIBLE IF SOMEONE TRY TO GET ANY IDEAS FROM IT AND BRICK HIS PHONE
I purchased Nokia 1 (TA-1047). My only objective was to automatically record sound from 8AM to 2 PM. So I started root process (Devmode: OK, boot loader unlock: OK, TWRP flashing and running: OK)
BUT WHAT? TWRP is asking for a password... this was not provided in the guide. I tried blank password... not OK. Then I searched the Internet and learned that if I cancel on password screen and then Wipe data then it will be fine. I did that, then made full backup (ADB), and flashed Magisk (ADB)..OK. Restarted the phone and "bump": Phone told me it failed to decrypt and then it went into TWRP boot-loop.
Then I searched again and found TA-1060 recovery bin (from this site) and stock images. I flashed TA-1060 recovery (at that time I did not know that I could go to Boot-loader from TWRP and wasted like an hour to do it using buttons - Correct method is: power off the phone, connect the usb cable, press power and volume down till you see android logo). After flashing 1060 recovery I was able to reset phone and "voila" Magisk was also there.
Now I installed Schedule Voice Recorder, Team-Viewer Host (to transfer big files remotely), App locker (to lock settings and play store), Autostart and Stay (because recorder was getting closed), Dropbox and Dropsync --- and you can guess what would have happened. My mobile kept closing them randomly even if I made Recorder and AutoStart system app and whitelisted in developer setting and set to NOT optimized battery. So I tried to disable Nokia bloat-wares and damaged the system again. This happened for a few iterations before I realized that the Nokia 1 RAM is not sufficient to handle all these apps and I got an idea to upload earlier android version (Spoiler! Hard-brick is coming).
I searched on internet for similar mobile and found Huawei Y3 2017 with same chipset and configuration, Y5 with same chipset but higher configuration. Downloaded stock rom for both. First tried flashing boot and system from TWRP but failed saying that size was different? Downloaded SP flash tool, somehow passed through drivers issue (this would require another thread ). Tried flashing (with formatting) both Y3 2017 UO00 (which was different chipset but i altered scatter file) and Y5 but it failed on some check error. After that my phone was hard bricked!
Then I downloaded nokia 1 stock firmware but it was bad scatter file (only nvram and nvdata was showing), altered it, format+flash: failed again. Searched on internet and found that if I flash wrong preloader then I am done. I was not sure if I had already done it. I altered the scatter file again to include only preloader and thankfully it showed success but any other rom after it, it failed to flash. Found something like Nokia 3 DA and tried it but also failed.
FINALLY: I found nokia 1 nb0 rom and nb0 extractor, extracted rom using that, flash it and "voila" my phone was back alive. Tried to root but failed (because serial number was not same as before and new number did not work). Then I started iterations by mixing roms from my backup and using my "proinfo.bin" and stock rom my phone revived with my own serial number. BUT, then I flashed stock preloader and lk but everything else from Huawei, it failed with check error and then also refused to format for stock rom. Searched on internet about manual formatting, did that (WARNING: starting from address where preloader ends otherwise you would format your preloader as well) then it was back okay.
Rooted again, copied scheduler in sys-priv, whitelisted, not optimize battery. Also team viewer host (normal settings) and dropbox and sync (normal settings). As a work around I have now scheduled the app to record 24 hours instead of 8AM to 2PM so that it always remain as foreground app. 11 hour testing so far so good.
QUESTION: Can I not upload lesser android version (e.g. 4.4 or 5 or 6)? If I can then how.?
UPDATE: The Recorder is killed by OS again as well as team viewer host (even when recorder apk was in system/priv-app)
Is there any way to keep it always ON?
Or is there any way to installed some previous version of android?
goodboy84h said:
UPDATE: The Recorder is killed by OS again as well as team viewer host (even when recorder apk was in system/priv-app)
Is there any way to keep it always ON?
Or is there any way to installed some previous version of android?
Click to expand...
Click to collapse
Every Nokia 1 user is facing background app crash problem. Infact Nokia 5 users also. It simply crashes background apps like pressing force close and as of now there is no solution. we have to wait until nokia releases a fix.
By the way which build number are you using?
coolboyforeva said:
Every Nokia 1 user is facing background app crash problem. Infact Nokia 5 users also. It simply crashes background apps like pressing force close and as of now there is no solution. we have to wait until nokia releases a fix.
By the way which build number are you using?
Click to expand...
Click to collapse
TA-1047
coolboyforeva said:
Every Nokia 1 user is facing background app crash problem. Infact Nokia 5 users also. It simply crashes background apps like pressing force close and as of now there is no solution. we have to wait until nokia releases a fix.
By the way which build number are you using?
Click to expand...
Click to collapse
Maybe you have so many apps in the background, I had Instagram, YouTube and Facebook life in the background and I get rare force closes or I might be lucky I have a Nokia 1 TA-1060
mattwhite7102 said:
Maybe you have so many apps in the background, I had Instagram, YouTube and Facebook life in the background and I get rare force closes or I might be lucky I have a Nokia 1 TA-1060
Click to expand...
Click to collapse
No its an os bug from nokia side. It fails to work as it should after a particular update. Maybe u r not facing coz u have only 3 apps that too light ones from good app makers, google and fb. But if u add some more like any call recorder ( as mentioned by op)u would also face same problem i believe. It doesnt thows a FC but simple kills the app in background and u dont get notified.
UPDATE :- Here is the solution
https://forum.xda-developers.com/showpost.php?p=77685710&postcount=4
goodboy84h said:
UPDATE: The Recorder is killed by OS again as well as team viewer host (even when recorder apk was in system/priv-app)
Is there any way to keep it always ON?
Or is there any way to installed some previous version of android?
Click to expand...
Click to collapse
Try this to avoid app crash. it works.
https://forum.xda-developers.com/showpost.php?p=77685710&postcount=4
HELP!!! Mine is stuck at Nokia logo screen
goodboy84h said:
I registered my account on this website just to share my awesome experience with Nokia 1.
I am very much thankful to XDA and many other sites whose text assisted me in recovering my mobile.
WARNING: VERY LARGE TEXT BELOW AND ITS JUST MY EXPERIENCE, I AM NOT RESPONSIBLE IF SOMEONE TRY TO GET ANY IDEAS FROM IT AND BRICK HIS PHONE
I purchased Nokia 1 (TA-1047). My only objective was to automatically record sound from 8AM to 2 PM. So I started root process (Devmode: OK, boot loader unlock: OK, TWRP flashing and running: OK)
BUT WHAT? TWRP is asking for a password... this was not provided in the guide. I tried blank password... not OK. Then I searched the Internet and learned that if I cancel on password screen and then Wipe data then it will be fine. I did that, then made full backup (ADB), and flashed Magisk (ADB)..OK. Restarted the phone and "bump": Phone told me it failed to decrypt and then it went into TWRP boot-loop.
Then I searched again and found TA-1060 recovery bin (from this site) and stock images. I flashed TA-1060 recovery (at that time I did not know that I could go to Boot-loader from TWRP and wasted like an hour to do it using buttons - Correct method is: power off the phone, connect the usb cable, press power and volume down till you see android logo). After flashing 1060 recovery I was able to reset phone and "voila" Magisk was also there.
Now I installed Schedule Voice Recorder, Team-Viewer Host (to transfer big files remotely), App locker (to lock settings and play store), Autostart and Stay (because recorder was getting closed), Dropbox and Dropsync --- and you can guess what would have happened. My mobile kept closing them randomly even if I made Recorder and AutoStart system app and whitelisted in developer setting and set to NOT optimized battery. So I tried to disable Nokia bloat-wares and damaged the system again. This happened for a few iterations before I realized that the Nokia 1 RAM is not sufficient to handle all these apps and I got an idea to upload earlier android version (Spoiler! Hard-brick is coming).
I searched on internet for similar mobile and found Huawei Y3 2017 with same chipset and configuration, Y5 with same chipset but higher configuration. Downloaded stock rom for both. First tried flashing boot and system from TWRP but failed saying that size was different? Downloaded SP flash tool, somehow passed through drivers issue (this would require another thread ). Tried flashing (with formatting) both Y3 2017 UO00 (which was different chipset but i altered scatter file) and Y5 but it failed on some check error. After that my phone was hard bricked!
Then I downloaded nokia 1 stock firmware but it was bad scatter file (only nvram and nvdata was showing), altered it, format+flash: failed again. Searched on internet and found that if I flash wrong preloader then I am done. I was not sure if I had already done it. I altered the scatter file again to include only preloader and thankfully it showed success but any other rom after it, it failed to flash. Found something like Nokia 3 DA and tried it but also failed.
FINALLY: I found nokia 1 nb0 rom and nb0 extractor, extracted rom using that, flash it and "voila" my phone was back alive. Tried to root but failed (because serial number was not same as before and new number did not work). Then I started iterations by mixing roms from my backup and using my "proinfo.bin" and stock rom my phone revived with my own serial number. BUT, then I flashed stock preloader and lk but everything else from Huawei, it failed with check error and then also refused to format for stock rom. Searched on internet about manual formatting, did that (WARNING: starting from address where preloader ends otherwise you would format your preloader as well) then it was back okay.
Rooted again, copied scheduler in sys-priv, whitelisted, not optimize battery. Also team viewer host (normal settings) and dropbox and sync (normal settings). As a work around I have now scheduled the app to record 24 hours instead of 8AM to 2PM so that it always remain as foreground app. 11 hour testing so far so good.
QUESTION: Can I not upload lesser android version (e.g. 4.4 or 5 or 6)? If I can then how.?
Click to expand...
Click to collapse
HELP: mine, TA-1047 is stuck at Nokia logo screen.
Please share me a life saver as you mentioned "I found nokia 1 nb0 rom and nb0 extractor, extracted rom using that, flash it and "voila" my phone was back alive."
I tried many many solutions like SP Flash Tool, Miracle Box, fastboot, .... but still failed and stuck.
I'm suffering day by day trying with no hope and now see your post. Please support me!
Much appreciate!
HELP!!!
My Nokia 1 (TA-1047) was hard bricked and won't turn on. I tried to flash my phone by SP Flashtool but my PC didn't recognize my phone. :crying::crying:
Could you give me the drivers you use and steps to recover my phone. Please help me. Thank u.
Hey all,
My phone updated today and ever since I cannot move past the initial lock screen. When unlocked, the UI appears to crash and send me back to the lock screen. My pin code works for turning the phone off, restarting the phone and putting it into emergency mode, which indicates some sort of UI crash.
Because this is a new account I can't post a link to a video of the issue directly, but the YouTube video code is: 8ZhlH-Tt-NU
I have tried the standard fixes like wiping the cache partition and booting into safe mode, but these don't seem to make any difference. Unfortunately I never logged into my Samsung account on this device, so their 'Find My Mobile' service is not an option. I am however signed into my Google account on the device and it does have wifi/network enabled.
The phone is running PPR1.180610.011/G965FXXU2CSA8
On the phones internal memory is a bunch of photos from a recent trip to Japan, I'm a fool for not backing these up sooner but I would hate to lose them.
Has anybody experienced anything like this before, and is there any way for me to get back into the phone, or atleast recover the photos that I took?
Thanks!
Edit:
One potential route out of this I can see is sideloading the same or a subsequent OTA update using ADB to hopefully fix the issue. Unfortunately despite some digging I can't find any updates that will allow installation from: PPR1.180610.011/G965FXXU2CSA8
If anybody has any information on this specific firmware version (Is it beta 3? beta 4? ect.), its installation path and where files relating to it may be listed/hosted it would be appreciated. Also how disasterous would it be to take a mismatched OTA upgrade and modify the metadata to allow it to be sideloaded onto the phone? I assume this would almost certainly break the OS completely but I'm not too sure.
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
profi_fahrer said:
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
Click to expand...
Click to collapse
Thanks for the reply Profi I had no idea using HOME_CSC would retain user data. I have tried flashing a few different versions of Pie (wish HOME_CSC) using Odin but with no luck, every time the phone boots I have the same problem. Do you know if there is a sure way to downgrade to Oreo while retaining user data? I have seen a few posts of people attemping this and getting stuck in bootloops, eventually requrining them to factory reset.
To give a final update on this. I attempted the Oreo downgrade, upon reboot the phone was stuck in a bootloop so I updated to Pie again. When the phone booted I tried the pin code as quickly as I could, and after some glitchy graphics on the screen it unlocked. From here I turn on the stay awake while plugged in feature in the developer options and managed to transfer all my data over to PC.
I don't believe it was the firmware changes that actually made any difference, because any further attempts to put my pin in, to remove the pin code for example, failed and cause the same crashing behaviour.
All data is recovered, I have factory reset the phone and all appears to be behaving as normal again. If anybody stumbles upon this with the same issue, all hope is not lost, but unfortunately I was unable to determine a realiable way to overcome it. It seems in this case it was just dumb luck.
Thanks for the assistance.
Hello, I write from Italy, where I bought an Honor 9 in December 2017.
I never tampered with this phone: no root, nor flashing, nor whatever fancy trick, as in fact I'm not really exactly good with smartphones.
The night between the 20th and the 21st of April 2019, after being prompted by my phone to install the new EMUI 9 update [ STF-L09 9.0.1.162(C432E2R1P5) ], I accepted and let it install overnight (note that the update was downloaded, probably automatically, 1 or 2 days before, but I didn't accept the prompt to install it yet, because I needed my phone for a 15-hours long car trip, and so I figured I wouldn't risk it by installing the update just before my trip - LUCKILY apparently, because otherwise I would have had to stay with this eRecovery thing the whole day without a computer).
I woke up this morning (21st of April) to find it was on eRecovery, giving me the following choices:
(some message I don't remember, probably "Serious problems occurred when the device boot etc. etc.")
Download latest version and recovery
Wipe data/factory reset
Reboot
Shutdown
I did the "Download latest version and recovery" option at first: after clicking it, it searches for WiFi around, and after writing my router password and connecting it to my router, it downloaded the 3941 MB (if I recall correctly) update; however, I left my phone downloading only to find it like this (I was away while it was downloading because I have a bit of a slow internet, so I don't exactly know what happens after it finishes downloading):
(some message I don't remember, probably "Serious problems occurred when the device boot etc. etc.")
Wipe data/factory reset
Shutdown
So I did "Shutdown" and I restarted the phone shortly after, and it restarted itself twice (one was my restart, but after that it restarted itself automatically), then always finishing on the eRecovery with 4 options like I wrote before. I did the "Download latest version and recovery" option again, and I had the same result.
What should I do? I really wish NOT to delete all my internal data, even because after reading some other threads I understood it might even be useless. Do you have any counsel?
Thanks in advance guys, I'm really going crazy and have no idea whatsoever about what to do, please help me!
P.S. I believe I found some other people with my same problem (or atleast similar) on the Huawei UK community site (I'm not allowed to post links yet as I just created this account).
The only way to recover this is download the update completely with pc in install to memory in dload folder after it finishes then boot to download mode and hopefully should work again it sounds like you have faulty update hope this helps
Try to update with HiSuite, if it doesn't work just grab your files with HiSuite and update using dload. If it still doesn't work, warranty claim.