Random reboot

mark12 Post time 2016-10-2 06:40:33 | Show all posts  Close [Copy link]
21 7111
Author: mark12

Random reboot

 Close [Copy link]

5

threads

40

posts

258

credits

Platinum Member

Rank: 3Rank: 3

credits
258
Post time 2016-9-20 02:46:38 | Show all posts
lets try one more time, i have asked this on multiple threads but no one seems to know anything, i received my umi super (euro edition) about 10 days ago, it came with this version installed (check image), i cant find any info on this firmware anywhere, can anyone help? the only issues i have with my phone is a delayed touch response in some apps/games, and my phone has rebooted 2 times in 10 days without warning, both times i had to force it off and power on again, is it possible that the euro edition is different than the standard editions?

14248067_10153764570116316_86270638_o (1).png

0

threads

3

posts

15

credits

New Member

Rank: 1

credits
15
Post time 2016-9-20 06:15:47 | Show all posts
gupise replied at 2016-9-20 02:35
Also my umi super was updated when arrived from gearbest, but, i guess with a firmware corrupt becau ...

Now also my smartphone run correctly, after of the downgrade to 20160708, Thanks

1

threads

5

posts

22

credits

New Member

Rank: 1

credits
22
Post time 2016-9-22 01:55:57 | Show all posts
Hi - I have the same issue - do you have to remove the battery when updating the ROM?

0

threads

15

posts

53

credits

Senior Member

Rank: 2

credits
53
Post time 2016-9-22 13:41:13 | Show all posts
cymruchris replied at 2016-9-22 01:55
Hi - I have the same issue - do you have to remove the battery when updating the ROM?

no!


2

threads

19

posts

79

credits

Senior Member

Rank: 2

credits
79
Post time 2016-9-25 04:30:44 | Show all posts
The fact we have to downgrade ROM shows how serious are UMI dev's when they release a new FOTA !!
Do they perform regression tests ? not sure...

0

threads

8

posts

43

credits

New Member

Rank: 1

credits
43
Post time 2016-9-26 16:35:35 | Show all posts
cymruchris replied at 2016-9-22 01:55
Hi - I have the same issue - do you have to remove the battery when updating the ROM?

No, but you will have to disable driver signature verification in order for the drivers to be correctly installed. Then just hit download and connect the phone powered off.

0

threads

8

posts

41

credits

New Member

Rank: 1

credits
41
Post time 2016-9-30 07:19:38 | Show all posts
Hello!
I still have same same problem with last update.
I can reproduce it reboot in the game like dawn of steel.

I was done hard reset, and reflash firmware.

0

threads

8

posts

41

credits

New Member

Rank: 1

credits
41
Post time 2016-10-1 17:15:57 | Show all posts
In my case firmware 20160708 doesn't solve problem.

0

threads

8

posts

41

credits

New Member

Rank: 1

credits
41
Post time 2016-10-1 22:01:10 | Show all posts
can it be for breaking battery?
Someone try change battery?

0

threads

8

posts

41

credits

New Member

Rank: 1

credits
41
Post time 2016-10-2 06:40:33 | Show all posts
Situation often difference, but now i catch bootloop:
"Start Android...
Optimization application 1 of 1."
Optimization could be doing endless, but one more time i catch log in logcat:
  1. 01-01 03:41:28.147   974  1073 W MountService: No primary storage defined yet; hacking together a stub
  2. 01-01 03:41:28.148   974  1073 W MountService: No primary storage defined yet; hacking together a stub
  3. 01-01 03:41:28.148   974  1073 W MountService: No primary storage mounted!
  4. 01-01 03:41:28.173   974   996 W AppOps  : Bad call: specified package null under uid 1000 but it is really -1
  5. 01-01 03:41:28.538   307   706 E AudioParamParser: appHandleThreadLoop(), inotify_add_watch failed !!! try again...
  6. 01-01 03:41:29.538   307   706 E AudioParamParser: appHandleThreadLoop(), inotify_add_watch failed !!! try again...
  7. 01-01 03:41:30.538   307   706 E AudioParamParser: appHandleThreadLoop(), inotify_add_watch failed !!! try again...
  8. 01-01 03:41:31.292  1106  1106 E         : Failed to opendir [/etc/mddb/]. err = [No such file or directory](2)
  9. 01-01 03:41:31.292  1106  1106 E         : Failed to find layout file in folder [/etc/mddb/].
  10. 01-01 03:41:31.292  1106  1106 E md_monitor: MonitorCore was not initialized successfully.
  11. 01-01 03:41:31.292  1106  1106 E md_monitor: InitMonitorCore fail
  12. 01-01 03:41:31.292  1106  1106 E md_monitor: Main: Exit EMDLogger with error.
  13. 01-01 03:41:31.539   307   706 E AudioParamParser: appHandleThreadLoop(), inotify_add_watch failed !!! try again...
  14. 01-01 03:41:32.539   307   706 E AudioParamParser: appHandleThreadLoop(), inotify_add_watch failed !!! try again...
  15. 01-01 03:41:33.539   307   706 E AudioParamParser: appHandleThreadLoop(), inotify_add_watch failed !!! try again...
  16. 01-01 03:41:34.540   307   706 E AudioParamParser: appHandleThreadLoop(), inotify_add_watch failed !!! try again...
  17. 01-01 03:41:34.955  1076  1100 W dex2oat : No verified method for method calling String.<init>: java.lang.String java.io.ByteArrayOutputStream.toString()
  18. 01-01 03:41:35.540   307   706 E AudioParamParser: appHandleThreadLoop(), inotify_add_watch failed !!! try again...
  19. 01-01 03:41:36.055  1076  1103 W dex2oat : No verified method for method calling String.<init>: java.lang.String java.io.ByteArrayOutputStream.toString()
  20. 01-01 03:41:36.334  1107  1107 E         : Failed to opendir [/etc/mddb/]. err = [No such file or directory](2)
  21. 01-01 03:41:36.334  1107  1107 E         : Failed to find layout file in folder [/etc/mddb/].
  22. 01-01 03:41:36.334  1107  1107 E md_monitor: MonitorCore was not initialized successfully.
  23. 01-01 03:41:36.334  1107  1107 E md_monitor: InitMonitorCore fail
  24. 01-01 03:41:36.334  1107  1107 E md_monitor: Main: Exit EMDLogger with error.
  25. 01-01 03:41:36.541   307   706 E AudioParamParser: appHandleThreadLoop(), inotify_add_watch failed !!! try again...
  26. 01-01 03:41:37.176  1076  1101 W dex2oat : Compilation of aocq aivo.mergeFrom(aocb) took 131.747ms
  27. 01-01 03:41:37.308  1076  1102 W dex2oat : Compilation of aocq aivm.mergeFrom(aocb) took 211.761ms
  28. 01-01 03:41:37.541   307   706 E AudioParamParser: appHandleThreadLoop(), inotify_add_watch failed !!! try again...
  29. --------- beginning of crash
  30. 01-01 03:41:37.801  1076  1105 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0xfe77fec0 in tid 1105 (Compiler driver)
  31. 01-01 03:41:37.806  1076  1102 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0xfefde450 in tid 1102 (Compiler driver)
  32. 01-01 03:41:37.807  1076  1100 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x114 in tid 1100 (Compiler driver)
  33. 01-01 03:41:37.808  1076  1099 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0xfefea2cc in tid 1099 (Compiler driver)
  34. 01-01 03:41:37.812   974  1094 F libc    : Fatal signal 4 (SIGILL), code 1, fault addr 0x7fa16fc9f4 in tid 1094 (hwuiTask1)
Copy the Code

After this messages phone would start boot again
123Next
You have to log in before you can reply Login | WELCOME TO UMIDIGI COMMUNITY

Points Rules

Quick Reply Top Back to list