Hello there. I've successfully reverted back to original fw. But because of the I've flashed custom rom and custom kernel, my Amazfit pace can't update firmware. It tries but appear triangle and ERROR message. How can I go back to "totally" stock? And I can receive updates..?
https://www.facebook.com/groups/227999507621434/permalink/267895556965162/
Thank you ?
oulouloul said:
Hello there. I've successfully reverted back to original fw. But because of the I've flashed custom rom and custom kernel, my Amazfit pace can't update firmware. It tries but appear triangle and ERROR message. How can I go back to "totally" stock? And I can receive updates..?
Click to expand...
Click to collapse
https://forum.xda-developers.com/smartwatch/amazfit/fw-tool-stock-firmware-installers-2017-t3725494
perhaps this could help
Related
Sup,
So, I flashed mutliple custom ROM's when I got this device like any other crack-flasher would but I then realised I much prefer it to be running stock with root access until an AOSP ROM comes along.
So I came from Omega 4.0 to stock LE8 in the UK, ever since I've flashed this stock ROM (Which is odexed) I keep getting the message "Sorry, messaging has unfortunately stopped" every time I open the app. I've tried wiping data/cache/dalvik and flashing in Odin again, same issues. I then went back to another custom ROM (HyperGalaxy) then went back to stock to test, still the same.
I have also tested an inverted AOSP 4.0.4 Mms app which worked on Omega, but didn't work on stock (Got the same message)
Data of the Messaging app has been wiped, i've disabled the app, rebooted, enabled again, still the same issues.
I've searched and I found 2 other threads with the same thing, but noone has been helpful enough yet.
It seems like the phone still thinks its running a Deodexed ROM but I need to get it back to full working order since I need to text something.
Any help is appreciated.
Try a factory reset...
Mopral said:
Try a factory reset...
Click to expand...
Click to collapse
Probably didn't make it clear enough, I did that already. 3 times to be exact.
i have the same issue. Need help.
i get this message with multiple apps.
all of them are standard run of the mill things like browser, messages, video player. My phone is only a week old and completely stock
some real bugs in this phone still that need sorting asap. poor effort by samsung really
Same issue here, has anyone found a fix for it yet?
I only encounter this in hyper x rom. So far so good in omega
Ok,I had this issue when I tried to install different firmware and modems using Mobile Odin. It fully resolved when I flashed back the official UK firmware and modem (le8) using normal desktop Odin. No force closes whatsoever since. Incidently, I'm now using LE9 firmware with UK CSC, rooted, with no issues at all. I used chainfires recovery, then flashed superuser to root.
Hope this helps.
nbhadusia said:
Ok,I had this issue when I tried to install different firmware and modems using Mobile Odin. It fully resolved when I flashed back the official UK firmware and modem (le8) using normal desktop Odin. No force closes whatsoever since. Incidently, I'm now using LE9 firmware with UK CSC, rooted, with no issues at all. I used chainfires recovery, then flashed superuser to root.
Hope this helps.
Click to expand...
Click to collapse
i got this everytime i clear cache and or wipe data from recovery before flashing new fw's.
so never wipe anything before flashing. if u already wiped, then flash it all over again and it will be all ok
my question is that i am flashing an old firmware
in order to have an old camera firmware version.
But my fw still remains the same ZDFF02.
Ani ideas how can i go back to ZDFE02?
bump
I'm interested in this too.
tried the same by flashing older firmware and writing back the old firmware but strangely it didnt happened.
any reason for downgrading?
bala_gamer said:
tried the same by flashing older firmware and writing back the old firmware but strangely it didnt happened.
any reason for downgrading?
Click to expand...
Click to collapse
Yeah bro
With newer fw my camera on CM10 isn't working, always shows " can't connect to camera".
With stock based roms it works perfectly.
Hi!
I flashed stock ICS C.1.0 using flashtool today.
I always get a message on startup saying (something along the lines of) 'The phone will restart in 15 minutes due to the battery draining during shipping'.
The phone doesn't restart in 15 mins. but the message is annoying.
I have had this phone for a lot of time (more than a year) and flashed many roms onto it. I have also flashed stock ICS C.1.0 many times before.
I never got this message before. I flashed stock ICS C.1.0 today from KitKat 4.4.2 and I got this message.
Any ideas on how to get rid of this message or what may have caused the problem?
Help appreciated.
Thanks!
Did you try another stock rom or use PC Companion ?
Nope. I will now. Thanks tho
Okay... I flashed ICS B.89 over C.1.0 (which gave me the problem) and I'm still getting it Help?
It says that I should insert a sim card to stop this message. Does this happen to you guys if you remove the sim card?
Coming from an MM eXistenZ installation (not sure what exact version, i think it was 5.6.5 final) I wanted to upgrade to O or at least N.
I have tried RR-O builds 20180316 and 20180213, RR-N 20171020 Final, CR-O 20180316, CR-N 20170918, but the result is always the same.
I get a smoothly running installation with only one obvious quirk: Whenever there are no apps running and the screen is off, after some amount of time (sometimes instantly, sometimes after 10 minutes or more) i can either not turn the screen on again and my phone reboots, or it reboots by itself without me interacting.
The only way I can reliably prevent my phone from crashing is playing music (via Spotify), even when muting media sound. While charging the phone will not reboot as well, until it reaches 100%
I tried different performance modes, with high performance resulting in (subjectively) worse results, i.e. reboots after a shorter amount of time, and almost thought energy saving mode would have fixed the problem as it worked for about 20 minutes, but then it began to reboot again.
I am using TWRP 3.2.1-1 and tried with/without Magisk (16.0) and flashing MarrowKernel (O-0.6, N-0.6/0.5).
Before flashing I performed a full wipe and also replaced the SD card
Logs from RR-N-v5.8.5-20171020-sirius-Final with Magisk 16.0 and MarrowKernel 0.6
dmesg: https:// cloud [DOT] haggi [DOT] me/index.php/s/C969nUuKTWMuJ1g
logcat: https:// cloud [DOT] haggi [DOT] me/index.php/s/as0qMPNYpGh4YKD
Sorry for the ugly links, but the logs are too long for a post, I cannot find an attachment option and as a new user may not post outgoing links yet
Please reflash Stock firmware via sony emma tool
This should help
Do not use existenz rom before switching to any custom rom reflash Always last stock and then update it to custom rom
Thank you, flashing stock firmware did the trick. Didn't work on the first try and my phone got stuck on the Sony bootscreen, but flashing the ROM a second time fixed the problem.
Running on RR-O now without any noticeable problems except for AudioFX crashing when sound starts/stops playing, but this should be fixed easily.
haggi94 said:
Thank you, flashing stock firmware did the trick. Didn't work on the first try and my phone got stuck on the Sony bootscreen, but flashing the ROM a second time fixed the problem.
Running on RR-O now without any noticeable problems except for AudioFX crashing when sound starts/stops playing, but this should be fixed easily.
Click to expand...
Click to collapse
Hi, did you root after flashing stock firmware ? or proceeded already to installation instructions ?
---------- Post added at 09:35 AM ---------- Previous post was at 08:46 AM ----------
rcstar6696 said:
Please reflash Stock firmware via sony emma tool
This should help
Do not use existenz rom before switching to any custom rom reflash Always last stock and then update it to custom rom
Click to expand...
Click to collapse
Hi Guru,
Do you recommend using Sony Emma Tool over Flashtool for flashing stock FTF ?
I would also like to try your ROMS, but I'm completely new on this device and not sure what to do when your installation instructions is to flash first stock ftf.
I wanna ask about Emma, does you recommend Emma for updating bootloader? I read in somewhere that if updating bootloader you cannot use stock ftf or restor TA backup cause it will kill the device. Is that true?
19iceman32 said:
Hi, did you root after flashing stock firmware ? or proceeded already to installation instructions ?
Click to expand...
Click to collapse
I have not rooted my phone after flashing stock FW
darknessmc said:
I wanna ask about Emma, does you recommend Emma for updating bootloader? I read in somewhere that if updating bootloader you cannot use stock ftf or restor TA backup cause it will kill the device. Is that true?
Click to expand...
Click to collapse
Sorry, I can't tell you as I continued flashing RR without having booted my phone in between and my TA partition is already lost since flashing the first custom ROM because I didn't know of it
I keep having an issue when returning to Stock/official Rom from Mokee100 on my NX611j
everytime I try, stock camera never works (I get a black screen when I try to launch).
I lost my original nandroid backup and am therefore helpless.
I get the black screen on 2.38, 2.45 and 2.49 rom versions.
Any pointers please?
I solved it by installing Stock firmware version 2.06.
That seemed to bring my camera back.