Related
I Just bought the new Fujitsu Arrows F-04E running android 4.0.4.
For now, there is nothing I could find on how to root it. I already tried the method of Bin4ry (Root MANY ANDROID) but didn't work. I'm now actively searching on Japanese sites, but nothing so far. If by chance someone in this community has some useful information that can help, please don't hesitate to share them. I will also share what I find, if any.
Thanks and hope we can figure the way to do it !
Cheers
The same with this enquire. If anybody enable to root and upgrade new Rom for F-04E, can u pls share for us? Thanks
luyenlt said:
The same with this enquire. If anybody enable to root and upgrade new Rom for F-04E, can u pls share for us? Thanks
Click to expand...
Click to collapse
More : If any one known the way to unlock !
phankhang said:
More : If any one known the way to unlock !
Click to expand...
Click to collapse
Please help if there are any solution . Thank all
root
1. Setup USB drivers on PC
2. Plug in Fujitsu Arrows V F-04E to PC (USB-debugging on)
3. Run root\runme.bat
am getting error
mount: Operation not permitted
Code:
-- F-02E ╥╗╝ⁿroot╣ñ╛▀ --
▒╛╚φ╝■└┤╫╘2ch┬█╠│íú└╢╔½dnxwj╝≥╥╫║║╗»íú
!! ╛»╕µ !!
1íóroot╓«║≤╜½╩º╚Ñ▒ú╨▐ú¼dnxwj║═╫≈╒▀╢╘┐╔─▄▓·╔·╬╩╠Γ▓╗╕║╚╬║╬╘≡╚╬íú
2íó┐¬╩╝root╘≥╩╙╬¬─π═¼╥Γ╫╘╨╨│╨╡ú╖τ╧╒íú
╟δ╫╘╨╨╫÷║├root╟░╫╝▒╕íú
PSú║╚⌠─·▓╗╧δrootú¼╟δ╓▒╜╙╣╪╡⌠╒Γ╕÷┤░┐┌íú
Press any key to continue . . .
╒²╘┌╕┤╓╞SuperUser...
╒²╘┌╚í╡├┴┘╩▒root...
989 KB/s (1283460 bytes in 1.267s)
1136 KB/s (146652 bytes in 0.126s)
867 KB/s (366952 bytes in 0.413s)
911 KB/s (1578585 bytes in 1.692s)
[+] This may take a few minutes.
[-] Failure.
╒²╘┌╜Γ│²LSM...
Mapping kernel memory...
Detected kernel physical address at 0x80008000 form iomem
Attempt fb_mem_exploit...
OK.
Finding kallsyms address in memory...
Segmentation fault (core dumped)
╒²╘┌╣╥╘┌/system╕─╬¬rw...
mount: Operation not permitted
╒²╘┌╠ß╔²SuperUser╚¿╧▐...
/system/xbin/su: cannot open for write: Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
╒²╘┌╓╪╨┬╣╥╘┌/system╬¬rw...
mount: Operation not permitted
╒²╘┌░▓╫░Superuser...
1140 KB/s (1578585 bytes in 1.352s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
╣º╧▓─·ú¼─·╡─F-02E╥╤╛¡│╔╣ªroot┴╦íú
Press any key to continue . . .
---------- Post added at 07:13 AM ---------- Previous post was at 07:08 AM ----------
i do have super user icon in my phone when i press install or recovery install it gives me "there was error installing superuser.please send a log of the error to the developer." but there is no log
also i checked with various apps to see if it was rooted but no it is not
did you got this resolved? USB debugging enabled on your device? did you install the driver correctly first?
m_ghv_geo said:
am getting error
mount: Operation not permitted
Code:
-- F-02E ╥╗╝ⁿroot╣ñ╛▀ --
▒╛╚φ╝■└┤╫╘2ch┬█╠│íú└╢╔½dnxwj╝≥╥╫║║╗»íú
!! ╛»╕µ !!
1íóroot╓«║≤╜½╩º╚Ñ▒ú╨▐ú¼dnxwj║═╫≈╒▀╢╘┐╔─▄▓·╔·╬╩╠Γ▓╗╕║╚╬║╬╘≡╚╬íú
2íó┐¬╩╝root╘≥╩╙╬¬─π═¼╥Γ╫╘╨╨│╨╡ú╖τ╧╒íú
╟δ╫╘╨╨╫÷║├root╟░╫╝▒╕íú
PSú║╚⌠─·▓╗╧δrootú¼╟δ╓▒╜╙╣╪╡⌠╒Γ╕÷┤░┐┌íú
Press any key to continue . . .
╒²╘┌╕┤╓╞SuperUser...
╒²╘┌╚í╡├┴┘╩▒root...
989 KB/s (1283460 bytes in 1.267s)
1136 KB/s (146652 bytes in 0.126s)
867 KB/s (366952 bytes in 0.413s)
911 KB/s (1578585 bytes in 1.692s)
[+] This may take a few minutes.
[-] Failure.
╒²╘┌╜Γ│²LSM...
Mapping kernel memory...
Detected kernel physical address at 0x80008000 form iomem
Attempt fb_mem_exploit...
OK.
Finding kallsyms address in memory...
Segmentation fault (core dumped)
╒²╘┌╣╥╘┌/system╕─╬¬rw...
mount: Operation not permitted
╒²╘┌╠ß╔²SuperUser╚¿╧▐...
/system/xbin/su: cannot open for write: Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
╒²╘┌╓╪╨┬╣╥╘┌/system╬¬rw...
mount: Operation not permitted
╒²╘┌░▓╫░Superuser...
1140 KB/s (1578585 bytes in 1.352s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
╣º╧▓─·ú¼─·╡─F-02E╥╤╛¡│╔╣ªroot┴╦íú
Press any key to continue . . .
---------- Post added at 07:13 AM ---------- Previous post was at 07:08 AM ----------
i do have super user icon in my phone when i press install or recovery install it gives me "there was error installing superuser.please send a log of the error to the developer." but there is no log
also i checked with various apps to see if it was rooted but no it is not
Click to expand...
Click to collapse
Your phone is F-02E. The root tool for F-04E
---------- Post added at 11:11 AM ---------- Previous post was at 11:06 AM ----------
m_ghv_geo said:
am getting error
mount: Operation not permitted
Code:
-- F-02E ╥╗╝ⁿroot╣ñ╛▀ --
▒╛╚φ╝■└┤╫╘2ch┬█╠│íú└╢╔½dnxwj╝≥╥╫║║╗»íú
!! ╛»╕µ !!
1íóroot╓«║≤╜½╩º╚Ñ▒ú╨▐ú¼dnxwj║═╫≈╒▀╢╘┐╔─▄▓·╔·╬╩╠Γ▓╗╕║╚╬║╬╘≡╚╬íú
2íó┐¬╩╝root╘≥╩╙╬¬─π═¼╥Γ╫╘╨╨│╨╡ú╖τ╧╒íú
╟δ╫╘╨╨╫÷║├root╟░╫╝▒╕íú
PSú║╚⌠─·▓╗╧δrootú¼╟δ╓▒╜╙╣╪╡⌠╒Γ╕÷┤░┐┌íú
Press any key to continue . . .
╒²╘┌╕┤╓╞SuperUser...
╒²╘┌╚í╡├┴┘╩▒root...
989 KB/s (1283460 bytes in 1.267s)
1136 KB/s (146652 bytes in 0.126s)
867 KB/s (366952 bytes in 0.413s)
911 KB/s (1578585 bytes in 1.692s)
[+] This may take a few minutes.
[-] Failure.
╒²╘┌╜Γ│²LSM...
Mapping kernel memory...
Detected kernel physical address at 0x80008000 form iomem
Attempt fb_mem_exploit...
OK.
Finding kallsyms address in memory...
Segmentation fault (core dumped)
╒²╘┌╣╥╘┌/system╕─╬¬rw...
mount: Operation not permitted
╒²╘┌╠ß╔²SuperUser╚¿╧▐...
/system/xbin/su: cannot open for write: Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
╒²╘┌╓╪╨┬╣╥╘┌/system╬¬rw...
mount: Operation not permitted
╒²╘┌░▓╫░Superuser...
1140 KB/s (1578585 bytes in 1.352s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
╣º╧▓─·ú¼─·╡─F-02E╥╤╛¡│╔╣ªroot┴╦íú
Press any key to continue . . .
---------- Post added at 07:13 AM ---------- Previous post was at 07:08 AM ----------
i do have super user icon in my phone when i press install or recovery install it gives me "there was error installing superuser.please send a log of the error to the developer." but there is no log
also i checked with various apps to see if it was rooted but no it is not
Click to expand...
Click to collapse
greatslon said:
1. Setup USB drivers on PC
2. Plug in Fujitsu Arrows V F-04E to PC (USB-debugging on)
3. Run root\runme.bat
Click to expand...
Click to collapse
You tried already, and is it successful rooted for F-04E?
Robiche said:
I Just bought the new Fujitsu Arrows F-04E running android 4.0.4.
For now, there is nothing I could find on how to root it. I already tried the method of Bin4ry (Root MANY ANDROID) but didn't work. I'm now actively searching on Japanese sites, but nothing so far. If by chance someone in this community has some useful information that can help, please don't hesitate to share them. I will also share what I find, if any.
Thanks and hope we can figure the way to do it !
Cheers
Click to expand...
Click to collapse
Hi bro,
Fujitsu F-04E rooted full
Pls checking some pictures below in attachment
If any support, feel free to contact me via YM: lethanhluyen
Hi,
I'm a noob at this stuff. I'm trying to root my f-04E. I've downloaded the two zip files, but I don't know how to install the usb drivers. I've tried installing them onto my SDK manager and still nothing happens. I've tried the runme option in the root file, but it says that my device is not detected. Any help would be awesome.
Phangtonpower said:
Hi,
I'm a noob at this stuff. I'm trying to root my f-04E. I've downloaded the two zip files, but I don't know how to install the usb drivers. I've tried installing them onto my SDK manager and still nothing happens. I've tried the runme option in the root file, but it says that my device is not detected. Any help would be awesome.
Click to expand...
Click to collapse
pls contact me for details
luyenlt said:
pls contact me for details
Click to expand...
Click to collapse
Actually I did send you a PM on here. Please check your in box
Is there anyone else with any ideas?
That we can have it posted here and have it documented for others to reference in the future.
Weekend bump.
About to call this one a lost cause bump
Thank you, was able to root no problem on the first try.
Although I did use generic google drivers. Sorry would link where I got them but cannot remember.
*update
Also wanted to mention that I have a EM01f, emobiles equivalent of this device.
*Update
though i was able to install superuser and passed rootchecker test i found I couldnt do a lot of things. So I downloaded the newest version of superuser renamed it to superuser.apk replaced the one in the zip and reran it. Works perfect, so far. Thanks again!
Hello to everyone I had an issue that was my phone restarts during calls and randomly, I just follow the root guide to eliminate all docomo bloatware
I root the phone successful but three days after a lot of app showed errors and restarts
When I restart phone the phone show three errors that are:
Com. Android. Phone process was closed and the Hceviewermaganer process has stopped and that situation is always on start
My phone doesn't work because this apps doesn't permit access to phone menu
Version of my phone is V16R
Question how I can try to reinstall original software, anyone has the recovery files to be uploaded through the recovery
Or any method to access through a Pc
Regards
Sent from my GT-I9300 using xda app-developers app
moku160 said:
Thank you, was able to root no problem on the first try.
Although I did use generic google drivers. Sorry would link where I got them but cannot remember.
*update
Also wanted to mention that I have a EM01f, emobiles equivalent of this device.
Click to expand...
Click to collapse
Hello !
I also have a EM-01F but I've the same problem as mentioned before. SuperUser icon is correctly installed on the device but when it's launched, an error pops to say me it can't install su access...
Which drivers have you used are what root program have you launched ?
Guigui_18892 said:
Hello !
I also have a EM-01F but I've the same problem as mentioned before. SuperUser icon is correctly installed on the device but when it's launched, an error pops to say me it can't install su access...
Which drivers have you used are what root program have you launched ?
Click to expand...
Click to collapse
check out my follow up post. I had to redo it, replacing the given superuser.apk without a newer version. THen it seemed to work correctly.
I'm using the droidrzr.com as ldirected in the roms section.
phase 3 fails:
Code:
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase three (this will take a minute)...
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File exists
Unable to chmod /data/logger: Operation not permitted
link failed File exists
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase four...
4558 KB/s (543080 bytes in 0.116s)
3804 KB/s (1867568 bytes in 0.479s)
3351 KB/s (476557 bytes in 0.138s)
3610 KB/s (63838 bytes in 0.017s)
[*] Cleaning up...
/system/bin/sh: su: not found
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Any suggestions.
I'm looking for a ROM to replace stock which supports USB OTG and allows disabling of the HDMI port. Wife passed her phone on to my son when we upgraded hers but its always detecting HDMI even if there is nothing plugged in. The disable detection setting in the stock JB rom only disabled for a short time.
Thanks
There be will be a video by therazrguy in YouTube for rooting all jellybean RAZRs.. That's an easy method...
You've to disable MotoDockService. Also i guess you're having the screen Force Portrait issue. If it's so, there's a root app to force orientation..
A friend of mine bought a refurbished RAZR and it has this issue
EugeneNine said:
I'm using the droidrzr.com as ldirected in the roms section.
phase 3 fails:
Code:
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase three (this will take a minute)...
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File exists
Unable to chmod /data/logger: Operation not permitted
link failed File exists
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase four...
4558 KB/s (543080 bytes in 0.116s)
3804 KB/s (1867568 bytes in 0.479s)
3351 KB/s (476557 bytes in 0.138s)
3610 KB/s (63838 bytes in 0.017s)
[*] Cleaning up...
/system/bin/sh: su: not found
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Any suggestions.
I'm looking for a ROM to replace stock which supports USB OTG and allows disabling of the HDMI port. Wife passed her phone on to my son when we upgraded hers but its always detecting HDMI even if there is nothing plugged in. The disable detection setting in the stock JB rom only disabled for a short time.
Thanks
Click to expand...
Click to collapse
install this and do it so easy
Kingo Android Root
Hi!
You can try to download this app :
http://www.mediafire.com/download/n...1.3.6_Cekas+FIX+Sharebertron.blogspot.com.apk
AFAIK it's mod-ed version of RootMaster, the mod makes it easier to understand the Chinese words.
You'll receive notification from Google prior to installing saying that this app is unsafe since it's trying to break the android secure, but I think it's all fine, rooted my 4.1.2 JB XT910, when I was in ICS, TheRAZRGuy's method worked for me but ever since I flashed JB it wont work anymore. This worked well for me, no problems so far.
Hope this helped!
Q&A for [Z Ultra][TWRP][PhilZ Touch][CWM] XZDualRecovery Q&A
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Z Ultra][TWRP][PhilZ Touch][CWM] XZDualRecovery Q&A. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Cannot go to recovery
I have installed this dual recovery to stock rom and i managed to change my rom to Cm11 snapshot which is a great rom. however i was trying to go to recovery and apparently im not going anywhere. Yellow LED light up but im not going to any recovery at all even after pressing volume up or down upon boot up. what am i doing wrong and what would be a possible fix for this? any help would be appreciated.:crying: thanks
rojculanag said:
I have installed this dual recovery to stock rom and i managed to change my rom to Cm11 snapshot which is a great rom. however i was trying to go to recovery and apparently im not going anywhere. Yellow LED light up but im not going to any recovery at all even after pressing volume up or down upon boot up. what am i doing wrong and what would be a possible fix for this? any help would be appreciated.:crying: thanks
Click to expand...
Click to collapse
CM11 will have over written this recovery when you installed it. Just after you start the boot the LED should go purple for a second or two, press the vol up key then and you should endup in CWM
blueether said:
CM11 will have over written this recovery when you installed it. Just after you start the boot the LED should go purple for a second or two, press the vol up key then and you should endup in CWM
Click to expand...
Click to collapse
Thank you for the reply mate. Thats"s what i thought also, i try to go to CWM,when purple LED lights up, i would press volume UP but it would just be stuck on SONY logo and yellow LED would light up and that's it. I have to restart the phone. is it ok to reflash the recovery? or would there be any step that I need to do. Thanks. Very appreciated.
rojculanag said:
Thank you for the reply mate. Thats"s what i thought also, i try to go to CWM,when purple LED lights up, i would press volume UP but it would just be stuck on SONY logo and yellow LED would light up and that's it. I have to restart the phone. is it ok to reflash the recovery? or would there be any step that I need to do. Thanks. Very appreciated.
Click to expand...
Click to collapse
try flashing the boot.img again or try another one (Carbon/DooMLoRD's/etc)
blueether said:
CM11 will have over written this recovery when you installed it. Just after you start the boot the LED should go purple for a second or two, press the vol up key then and you should endup in CWM
Click to expand...
Click to collapse
blueether said:
try flashing the boot.img again or try another one (Carbon/DooMLoRD's/etc)
Click to expand...
Click to collapse
thanks. I finally was able to do it. thank you. now im trying out Android Lollipop Port and it's great.
Code:
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices! =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?3
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting ro.build.product
=============================================
Device model is C6833
Firmware is 14.4.A.0.108
=============================================
Step2 : Sending the recovery files.
=============================================
mkdir failed for /data/local/tmp/recovery, File exists
0 KB/s (29 bytes in 1.000s)
15387 KB/s (15757 bytes in 0.001s)
0 KB/s (501 bytes in 1.000s)
11 KB/s (11842 bytes in 1.000s)
1790 KB/s (56834 bytes in 0.031s)
334 KB/s (3082 bytes in 0.009s)
0 KB/s (385 bytes in 1.000s)
1794 KB/s (657704 bytes in 0.358s)
1996 KB/s (2965760 bytes in 1.451s)
2494 KB/s (2599934 bytes in 1.018s)
2142 KB/s (1875823 bytes in 0.855s)
855 KB/s (8759 bytes in 0.010s)
=============================================
Step3 : Setup of dual recovery.
=============================================
=============================================
Attempting to get root access for installation using TowelRoot now.
NOTE: this only works on certain ROM/Kernel versions!
If it fails, please check the development thread (Post #2) on XDA for more detai
ls.
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app!!
You can use one of the recoveries to root your device.
=============================================
=============================================
Sending files
=============================================
153 KB/s (1572 bytes in 0.010s)
1659 KB/s (13592 bytes in 0.008s)
cannot stat 'easyroottool\libexploit.so': No such file or directory
545 KB/s (9496 bytes in 0.017s)
1335 KB/s (13672 bytes in 0.010s)
Copying kernel module...
1122 KB/s (34473 bytes in 0.030s)
0 KB/s (765 bytes in 1.000s)
1659 KB/s (13592 bytes in 0.008s)
Kernel version is 3.4.0-perf-g0109737
Version does not match 3.4.0-perf-ge4322cd, needs patching...
1+0 records in
0+1 records out
19 bytes transferred in 0.001 secs (19000 bytes/sec)
Kernel module patched.
modulecrcpatch (by zxz0O0)
module_layout: match
__aeabi_unwind_cpp_pr1: match
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match
successfully patched
=============================================
Installing using zxz0O0's towelzxperia
(using geohot's towelroot library)
=============================================
towelzxperia (by zxz0O0)
thanks to geohot for libexploit
creating libzxploit.so
error: Could not open libexploit.so
/system/bin/sh: /system/xbin/busybox: not found
=============================================
Installation finished. Enjoy the recoveries!
=============================================
Aby kontynuować, naciśnij dowolny klawisz . . .
What am I doing wrong? Can anyone help? I have tried on the second laptop with the same result. Windows 7 x64.
Never mind. I didn't turn off antivirus.
Hi..
Wondering if I'm able to flash these cwm/ twrp
Into my togari 6833 (xperia z ultra)?
Error while installing on C6802 Xperia Z Ultra
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices! =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
error: more than one device and emulator
Device found!
=============================================
Getting ro.build.product
=============================================
error: more than one device and emulator
Device model is
error: more than one device and emulator
Firmware is
=============================================
Step2 : Sending the recovery files.
=============================================
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
=============================================
Step3 : Setup of dual recovery.
=============================================
error: more than one device and emulator
error: more than one device and emulator
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
error: more than one device and emulator
Press any key to continue . . .
error: more than one device and emulator
error: protocol fault (status read)
error: more than one device and emulator
error: more than one device and emulator
=============================================
Installation FAILED!
Please copy and paste the contents of this
window to the DevDB thread for troubleshooting!
=============================================
Press any key to continue . . .
Problem while switching to recovery..
I installed recovery properly..
But when I am trying to switch recovery mod, It is directly switch on..
I am using a latest firmware 14.4.A.0.108..
Is there any solution for it??
I installed this successfully on my Z ULtra. However when I tried to do a nandroid backup or flash a custom rom i always face this error : cannot mount system ??
ANy solution to this ?
Thanks
Issues with Dual Boot Recovery
Hi,
Anyone can help me out?
I have an Xperia Z Ultra, freshly rooted with unlocked BL.
I installed Dual Recovery but for some reason, I can't reboot to any of the recovery this has to offer (PhilTouch, CWM, and TWRP).
Tried the physical button method and via NDR Utils with no success.
Looking at the log on the console, it looks like it failed to copy some files saying that a given directory is read-only but I checked using ES File Explorer that these directories are writable.
Can anyone help out as I would like to create a nandroid backup before messing with anything else just in case.
Anyway, here is the output of the installer console:
===========================================================
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices! =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting ro.build.product
=============================================
Device model is C6833
Firmware is 14.4.A.0.108
=============================================
Step2 : Sending the recovery files.
=============================================
19 KB/s (30 bytes in 0.001s)
4728 KB/s (16947 bytes in 0.003s)
326 KB/s (501 bytes in 0.001s)
4656 KB/s (11920 bytes in 0.002s)
5842 KB/s (56834 bytes in 0.009s)
1504 KB/s (3082 bytes in 0.002s)
3271 KB/s (30148 bytes in 0.009s)
453 KB/s (1162 bytes in 0.002s)
2805 KB/s (34473 bytes in 0.012s)
225 KB/s (924 bytes in 0.004s)
1896 KB/s (13592 bytes in 0.007s)
375 KB/s (385 bytes in 0.001s)
5405 KB/s (719520 bytes in 0.130s)
5668 KB/s (3419065 bytes in 0.589s)
5123 KB/s (2431545 bytes in 0.463s)
6589 KB/s (1936442 bytes in 0.287s)
3477 KB/s (8902 bytes in 0.002s)
=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
-rwxr-xr-x 1 shell shell 719520 Apr 8 14:27 /data/local/tmp/recover
y/busybox
Press any key to continue . . .
##########################################################
#
# Installing XZDR version 2.8.5 RELEASE
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to al
low installation.
insmod: can't insert '/system/lib/modules/wp_mod.ko': File exists
Copy recovery files to system.
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy disableric to system.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event5!
sed: can't create temp file '/storage/sdcard1/XZDualRecovery/XZDR.propGnS20I': R
ead-only file system
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event4!
sed: can't create temp file '/storage/sdcard1/XZDualRecovery/XZDR.propUUaD89': R
ead-only file system
Speeding up backups.
touch: /sdcard1/clockworkmod/.hidenandroidprogress: Read-only file system
Make sure firstboot goes to recovery.
sed: can't create temp file '/storage/sdcard1/XZDualRecovery/XZDR.propTcsuIy': R
ead-only file system
sed: can't create temp file '/storage/sdcard1/XZDualRecovery/XZDR.propT1eL2g': R
ead-only file system
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================
=============================================
Installation finished. Enjoy the recoveries!
=============================================
Press any key to continue . . .
=============================================
Hi sorry I just want to see if anyone can help me with my z ultra I can't get it to enter recovery with the hardware keys and the rom isn't working correctly so I can't do anything when It turns on all help appreciated
Anyone?
@[NUT], assistance please?
Thanx!
Resolved!
I removed the installation using the guide on the original thread and reinstalled a newly downloaded version (ZU-lockeddualrecovery2.8.8-RELEASE.installer.zip)
Just thought I'd place a feedback here.
Thanks!
Can this be installed on purely stock unrooted firmware? I'm on Lollipop .270.
Sent from my LG-F320L using Tapatalk
Failed install ZU Dual Recovery
Hi... sorry, i want to see if anyone can help me with my Z Ultra C6833 build number 14.4.A.0.108, I am failed install recovery.
Can anyone help me out, until success install Dual Recovery...
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices! =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
error: protocol fault (status read)
Device found!
=============================================
Getting ro.build.product
=============================================
error: more than one device and emulator
Device model is
error: more than one device and emulator
Firmware is
=============================================
Step2 : Sending the recovery files.
=============================================
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
=============================================
Step3 : Setup of dual recovery.
=============================================
error: more than one device and emulator
error: more than one device and emulator
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
error: more than one device and emulator
Press any key to continue . . .
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
=============================================
Installation FAILED!
Please copy and paste the contents of this
window to the DevDB thread for troubleshooting!
=============================================
Press any key to continue . . .
Hello I'm using a Xperia z ultra c6833 running stock lollipop 5.2 I have done nothing on it i dont have root my bootloader is locked keep in mind that lollipop has some problems I want to install a coustem rom can I use this method is there any other way please help me I'm losing hop please help
---------- Post added at 12:35 PM ---------- Previous post was at 12:14 PM ----------
Hello I'm using a Xperia z ultra c6833 running stock sony lollipop 5.0.2 I don't have root access and my bootloader is locked since lollipop has problems and it's really hard to get a coustem recovery in my situation can I use this method is there any other way I'm losing hop can any one please help
BREAKING NEWS:
Huami took down the files from my hoster because of "alleged copyright infringement". I got a notice and an information that the files have been deleted, as well as that any further copyright infringement will lead to termination of the account and possible legal activities.
UPDATE 23-06-2017:
I updated the files to version 1.3.3a and reuploaded them to a different fileshare. (Let's see if they will be taken down again...)
UPDATE:
This is a new conversion method based on the techniques I used in my PACEfied installer. It will install the official Huami English firmware 1.3.3a with all features and OTA enabled. It will, however, NOT lock your bootloader. So, you have some time to evaluate, if you like the official ROM, or prefer to go to the PACEfied ROM.
NOTE: AS SOON AS YOU RECEIVE AND INSTALL AN OFFICIAL OTA AFTERWARDS, YOUR BOOTLOADER WILL BE LOCKED AND YOU WILL NOT BE ABLE TO SWITCH BACK.
ATTENTION: THIS METHOD ONLY WORKS FOR WATCHES WITH UNLOCKED BOOTLOADER (Huami started locking in official firmware 1.2.13 / 1.3.2b and upwards).
INSTALLATION:
This method uses the same installation procedure as PACEfied. Please find all information here: https://gitlab.com/Neuer_User/PACEfied_AmazFit/wikis/permanent-install
Downloads:
OFFICIAL ENGLISH FIRMWARE 1.3.3a: https://app.box.com/s/3io4m4zk7775x3vp80yw19l52slk6sxs
NOTE:
It is recommended that you factory reset the watch after installation, as data from other ROMs may lead to force closes of apps. You can do this either by unpairing the watch or in the settings / device menu of the watch.
DISCLAIMER:
While this method is pretty safe, there is a chance that you may brick your watch (so far no case known). YOU DO THIS ON YOUR OWN RISK. I am not responsible for any damages, psychological problems or wars emerging out of you converting your watch.
With the help of Neuer I was to flash my smartwatch with US Image!
I had some problems regarding android drivers while running fastboot and adb steps, this is how I solved them:
if fastboot is not detecting your device just download/install Google USB Driver at:
https://developer.android.com/studio/run/win-usb.html
Follow this guide on how to install the driver:
http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/3/
Neuer_User said:
Hi guys
...
fastboot boot Amazfit-mod-recovery.img
...
Click to expand...
Click to collapse
After booting into the modded recovery, adb was not detecting my smartwatch. All that i had to do was to go to "Step 35" of the previous guide and install the "Android Composite ADB Interface" driver and everything started to work again with ADB.
Big thanks to Neuer for his amazing hard work and patience! He did it! Also big thanks to everyone that provided useful information for this to work.
The instructions are good.
Model is now A1612.
ROM Version is now 1.3.0n
I cannot switch from Mi to KM.
Hi all,
Big thanks to Neuer_User for his hard work!
Just a quick question for those who have converted into english: does sync work and in which app (strava or mifit)?
Thanks.
It works perfectly. Thank you very much Neuer.
Great work Neuer_User you are now officialy a Amazfit Legend!!
May i suggest the next person to attempt this does a video tutorial and uploads it to youtube. Kudos to all those who have contributed in one way or another.
Another XDA Headline
I've an error during update, do you have any hint:
Code:
C:\Downloads\convert_to_eng>adb push boot.img.gz /sdcard/
7573 KB/s (5575879 bytes in 0.719s)
C:\Downloads\convert_to_eng>adb push system.img.gz /sdcard/
7713 KB/s (189626362 bytes in 24.009s)
C:\Downloads\convert_to_eng>adb push flash_eng_version.sh /sdcard
/
267 KB/s (547 bytes in 0.002s)
C:\Downloads\convert_to_eng>adb push md5s.txt /sdcard/
45 KB/s (94 bytes in 0.002s)
C:\Downloads\convert_to_eng>adb shell reboot bootloader
C:\Downloads\convert_to_eng>fastboot devices
0123456789 fastboot
C:\Downloads\convert_to_eng>fastboot boot Amazfit-mod-recovery.im
g
downloading 'boot.img'...
OKAY [ 0.436s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.403s
Thank you so much. it worked perfectly.
Can you make a tutorial movie ?? Im not very good whit fastboot. Tks
perritos said:
I've an error during update, do you have any hint:
C:\Downloads\convert_to_eng>adb push boot.img.gz /sdcard/
7573 KB/s (5575879 bytes in 0.719s)
C:\Downloads\convert_to_eng>adb push system.img.gz /sdcard/
7713 KB/s (189626362 bytes in 24.009s)
C:\Downloads\convert_to_eng>adb push flash_eng_version.sh /sdcard
/
267 KB/s (547 bytes in 0.002s)
C:\Downloads\convert_to_eng>adb push md5s.txt /sdcard/
45 KB/s (94 bytes in 0.002s)
C:\Downloads\convert_to_eng>adb shell reboot bootloader
C:\Downloads\convert_to_eng>fastboot devices
0123456789 fastboot
C:\Downloads\convert_to_eng>fastboot boot Amazfit-mod-recovery.im
g
downloading 'boot.img'...
OKAY [ 0.436s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.403s
Click to expand...
Click to collapse
That is no error. You just need to continue with the next step. You should be recovery now and need to start adb.
Neuer_User said:
That is no error. You just need to continue with the next step. You should be recovery now and need to start adb.
Click to expand...
Click to collapse
That's ok
Now my amazfit is in English version.
Thanks very much
Great job!!
Flawless instructions. Worked beautifuly.
I'd have made a video but was paranoid enough that something might go wrong that I didn't want to be distracted during the process. Anyway, the instructions are so clear I'm not sure someone needs the video. So long as adb/fastboot is set up properly, all will go fine.
Perfect, it works for me.
Flashed, rebooting.........
All ok thanks my friends!
Just to inform, during the procedure I have had a problem, after
"fastboot boot Amazfit-mod-recovery.img"
I have had an error message, but I move on because after adb shell I was root "#"
Thank you very much Great Job
Thanks you very much
I apply and all is ok
Thanks you again
took the plunge, all good... top work!
Thanks, guys, for all the positive feedback. I'm happy to hear it is working.
Presumably after flash we can delete these pushed files from SD card to free up storage space?
Sent from my HUAWEI NXT-L29 using XDA Free mobile app
Thank you ! Done ! It's all right !
Just a question : We can't get 24-hour clock instead AM/PM ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THIS WILL NOT WORK ON AMAZFIT PACE OR AMAZFIT STRATOS
THIS WILL NOT WORK ON AMAZFIT PACE OR AMAZFIT STRATOS
THIS WILL NOT WORK ON AMAZFIT PACE OR AMAZFIT STRATOS
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please make sure you read and understand everything written in the post before flashing it! YOU are choosing to make these modifications and must be sure of what it does.
Click to expand...
Click to collapse
Only for unlocked Bootloader
Supported devices: A1801 (Chinese) and A1811 (English)
Property installed ADB and Fastboot drivers as system wide
Watch battery +40% (50% recommended)
Click to expand...
Click to collapse
For anyone interested on installing Stock/Original Chinese Firmware with OTA updates.
Click to expand...
Click to collapse
@Neur_User for PACEfied, STRATOSfied projects and other stuff
@Cracklydisc for AmazIT, StratOS projects and other stuff
Capara @1immortal for his great support
Click to expand...
Click to collapse
1. Connect the watch to your PC
2. Unzip the the folder
3. Run flash_US.bat file for English interface (Don't do it as Administrator since is known to cause issues)
4. Wait to the end of the process and don't touch anything
********************************************************
CN Verge 3.0.12.0 Stock Firmware Installer by Saratoga
********************************************************
1. Connect the watch to the PC
********************************
*******************************
2. Rebooting to Fastboot mode
*******************************
****************************
3. Checking the connection
****************************
****************************
4. Booting modded recovery
****************************
< waiting for any device >
Downloading 'boot.img' OKAY [ 0.464s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.535s
***********************************
5. Waiting connection in Recovery
***********************************
******************
6. Copying files
******************
boot.img: 1 file pushed. 7.3 MB/s (9437184 bytes in 1.232s)
system.img.gz: 1 file pushed. 5.1 MB/s (318817711 bytes in 60.127s)
md5s.txt: 1 file pushed. 0.0 MB/s (91 bytes in 0.002s)
flash_rom.sh: 1 file pushed. 0.2 MB/s (458 bytes in 0.002s)
**************************
7. Firmware installation
**************************
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.924353 seconds, 9.7MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 96.290046 seconds, 8.6MB/s
Finished
*******************
8. Removing files
*******************
**************
9. Rebooting
**************
*************************************
10. Changing language to Chinese
*************************************
List of devices attached
d41e250a device
**************************************
Stock recovery installation process
**************************************
********************************
11. Rebooting to Fastboot mode
********************************
***************************
12. Booting temporal root
***************************
< waiting for any device >
Downloading 'boot.img' OKAY [ 0.373s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.422s
*******************
13. Copying files
*******************
install_recovery.sh: 1 file pushed. 0.2 MB/s (687 bytes in 0.003s)
recovery.img: 1 file pushed. 2.8 MB/s (16777216 bytes in 5.662s)
*****************************
14. Flashing Stock recovery
*****************************
============= STOCK Installer ===============
Done. OTA updates should now work.
*******************
15. Removing files
*******************
***************
16. Rebooting
***************
************
17. Finish
************
Presione una tecla para continuar . . .
Click to expand...
Click to collapse
* Step 14 may be different for you
Click to expand...
Click to collapse
Latest version
Stock CN/Chinese 3.0.43.0 Firmware Installer with OTA updates | Mirror
Previous versions
Stock CN/Chinese 3.0.29.0 Firmware Installer with OTA updates | Mirror
Stock CN/Chinese 3.0.12.0 Firmware Installer with OTA updates | Mirror
Stock CN/Chinese 3.0.10.0 Firmware Installer with OTA updates | Mirror
Click to expand...
Click to collapse
If you like my work you can buy me a beer here
Click to expand...
Click to collapse
Manual Installation Method
Manual Installation Method
Introduction
Here I will explain how to install the firmware using a command window or any other terminal.
The requirements are the ones stated in Post #1.
On your terminal, go to the path where all the files were unzipped and you are good to go.
Manual command installation
You can copy and paste all needed commands.
Firmware installation
1. Connect the watch to the PC and check the connection with the watch
Code:
[COLOR="Blue"]adb devices[/COLOR]
Output (or similar)
Code:
List of devices attached
9dee1d33 device
2. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
3. When the watch reboots in fastboot mode, check the connection with the watch
Code:
[COLOR="blue"]fastboot devices[/COLOR]
Output (or similar)
Code:
0123456789 fastboot
4. Boot the modded recovery
Code:
[COLOR="blue"]fastboot boot recovery-mod.img[/COLOR]
Output (or similar)
Code:
downloading 'boot.img'...
OKAY [ 0.426s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.303s
5. Wait until you get a triangle with an exclamation mark (!) in your watch
6. Copy the files to the watch (it may take upto a minute)
Code:
[COLOR="blue"]adb push boot.img /data/media/0/
adb push system.img.gz /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/[/COLOR]
Output (or similar)
Code:
adb push boot.img /data/media/0/
7546 KB/s (9437184 bytes in 1.221s)
adb push system.img.gz /data/media/0/
7194 KB/s (228153632 bytes in 30.969s)
adb push md5s.txt /data/media/0/
88 KB/s (91 bytes in 0.001s)
adb push flash_rom.sh /data/media/0/
297 KB/s (458 bytes in 0.001s)
7. Start Firmware installation (it may take up to 2 minutes)
Code:
[COLOR="blue"]adb shell sh /data/media/0/flash_rom.sh[/COLOR]
Output (or similar)
Code:
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.953804 seconds, 9.4MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 89.945101 seconds, 9.2MB/s
Finished
8. We have already installed the firmware, now delete installation files form the watch
Code:
[COLOR="blue"]adb shell rm /data/media/0/boot.img
adb shell rm /data/media/0/system.img.gz
adb shell rm /data/media/0/md5s.txt
adb shell rm /data/media/0/flash_rom.sh[/COLOR]
9. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
10. When the splash screen is passed and the bootanimation starts, set your watch to Chinese language
Code:
[COLOR="blue"]adb shell setprop persist.sys.language zh
adb shell setprop persist.sys.country CN[/COLOR]
Stock recovery installation process
11. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
12. Boot temporal root
Code:
[COLOR="blue"]fastboot boot boot-CN-adb-root.img[/COLOR]
Output (or similar)
Code:
downloading 'boot.img'...
OKAY [ 0.349s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.206s
13. Copy stock recovery files to the watch
Code:
[COLOR="blue"]adb push install_recovery.sh /data/media/0/
adb push recovery.img /data/media/0/[/COLOR]
Output (or similar)
Code:
[100%] /data/media/0/install_recovery.sh
[100%] /data/media/0/recovery.img
14. Run the recovery installation script
Code:
[COLOR="blue"]adb shell cd /data/media/0/; sh install_recovery.sh[/COLOR]
Or if above command doesn't work, do it in 2 commands
Code:
[COLOR="blue"]adb shell cd /data/media/0/
adb shell sh install_recovery.sh[/COLOR]
Output (or similar)
Code:
============= STOCK Installer ===============
Flashing recovery...
4096+0 records in
4096+0 records out
16777216 bytes (16.0MB) copied, 2.461221 seconds, 6.5MB/s
Done. OTA updates should now work.
15 . Delete stock recovery installation files
Code:
[COLOR="blue"]adb shell rm /data/media/0/install_recovery.sh
adb shell rm /data/media/0/recovery.img [/COLOR]
16. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
17. Finish.
Go to Amazfit app and update to latest version.
Some extra useful commands
Wipe dalvik/cache
Code:
[COLOR="blue"]adb shell reboot bootloader
fastboot erase cache
fastboot reboot[/COLOR]
Do a Factory Reset (You will lose all the data in your watch. Unpair the watch from Amazfit app while doing this?
Code:
[COLOR="Blue"]adb shell reboot bootloader
fastboot erase data
fastboot erase cache
fastboot reboot[/COLOR]
Reserved 1
Reserved 1
I tried flashing back from 3.2.0.5 back.
First error at Step 4 when the recovery-mod.img is flashed to boot and the booting failed.
****************************
4. Booting modded recovery
****************************
< waiting for any device >
Downloading 'boot.img' FAILED (status read failed (Too many links))
Finished. Total time: 1.082s
***********************************
5. Waiting connection in Recovery
***********************************
So I have to do manually:
\Verge_Stock_CN_3.0.12.0_Firmware_Installer>fastboot boot recovery-mod.img
Downloading 'boot.img' OKAY [ 0.464s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.545s
2nd error is during the flash prompt, ADB exited shell before system flash is completed:
Step 7 no flash system complete message
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell sh /data/media/0/flash_rom.sh
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.952945 seconds, 9.4MB/s
Flashing system.img
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>
Took me a while to re-connect to shell and reissue the flash command.
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell sh /data/media/0/flash_rom.sh
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb reconnect
reconnecting c5121c27 [connecting]
Finally able to reconnect to shell
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
# ls
cache
charger
data
default.prop
dev
etc
file_contexts
flash
fstab.watch
init
init.rc
init.recovery.watch.rc
mnt
proc
res
root
sbin
sdcard
sepolicy
sideload
sys
system
tmp
ueventd.rc
ueventd.watch.rc
# ls data/media/0
Alarms
DCIM
Download
Movies
Music
Notifications
Pictures
Podcasts
Ringtones
WatchFace
boot.img
flash_rom.sh
gpxdata
md5s.txt
system.img.gz
# sh /data/media/0/flash_rom.sh
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.950465 seconds, 9.5MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 101.986899 seconds, 8.1MB/s
Finished
After rebooting I am able to receive 3.0.13.0 OTA and install.
apollow2007 said:
I tried flashing back from 3.2.0.5 back.
First error at Step 4 when the recovery-mod.img is flashed to boot and the booting failed.
****************************
4. Booting modded recovery
****************************
< waiting for any device >
Downloading 'boot.img' FAILED (status read failed (Too many links))
Finished. Total time: 1.082s
***********************************
5. Waiting connection in Recovery
***********************************
So I have to do manually:
\Verge_Stock_CN_3.0.12.0_Firmware_Installer>fastboot boot recovery-mod.img
Downloading 'boot.img' OKAY [ 0.464s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.545s
2nd error is during the flash prompt, ADB exited shell before system flash is completed:
Step 7 no flash system complete message
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell sh /data/media/0/flash_rom.sh
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.952945 seconds, 9.4MB/s
Flashing system.img
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>
Took me a while to re-connect to shell and reissue the flash command.
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell sh /data/media/0/flash_rom.sh
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
error: device still connecting
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb reconnect
reconnecting c5121c27 [connecting]
Finally able to reconnect to shell
E:\downloads\watch\Verge_Stock_CN_3.0.12.0_Firmware_Installer>adb shell
# ls
cache
charger
data
default.prop
dev
etc
file_contexts
flash
fstab.watch
init
init.rc
init.recovery.watch.rc
mnt
proc
res
root
sbin
sdcard
sepolicy
sideload
sys
system
tmp
ueventd.rc
ueventd.watch.rc
# ls data/media/0
Alarms
DCIM
Download
Movies
Music
Notifications
Pictures
Podcasts
Ringtones
WatchFace
boot.img
flash_rom.sh
gpxdata
md5s.txt
system.img.gz
# sh /data/media/0/flash_rom.sh
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 0.950465 seconds, 9.5MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 101.986899 seconds, 8.1MB/s
Finished
After rebooting I am able to receive 3.0.13.0 OTA and install.
Click to expand...
Click to collapse
Glad you were able to install and update.
May I ask for your Windows version and previous ROM version on watch?
Saratoga79 said:
Glad you were able to install and update.
May I ask for your Windows version and previous ROM version on watch?
Click to expand...
Click to collapse
Windows 10 Pro.
Previous ROM was 3.2.0.5 which was converted from 3.0.13.0.
Stock 3.0.14.0 firmware if you want it.
Great work Saratoga79.
My Verge prompted me for an update this morning, I have stock 3.0.14.0 (zh but set to en) on it if you want a copy.
Hi.
Possible to update the ROM image here to 3.0.29.0?
Flashing back from US to CN rom will have to start update from 3.0.14 all the way to 3.0.29.0
apollow2007 said:
Hi.
Possible to update the ROM image here to 3.0.29.0?
Flashing back from US to CN rom will have to start update from 3.0.14 all the way to 3.0.29.0
Click to expand...
Click to collapse
OP updated with 3.0.29.0 Firmware Installer.
Ayuda!
I have the 1801 version of China. With room 3.0.28 of saratoga, but I constantly get request to update to official 3.0.29. So how do I give an update and do not miss the Spanish language?
Sliv33 said:
I have the 1801 version of China. With room 3.0.28 of saratoga, but I constantly get request to update to official 3.0.29. So how do I give an update and do not miss the Spanish language?
Click to expand...
Click to collapse
My ROM is since a week ago based on 3.0.29.0.
Hello people , I have verge that keeps freezing when receiving several notifications and has sever battery drain. I have factory reset and re-installed the English firmware . But doesn't seem to help.
Will installing the latest Chinese firmware help.
Than I can install the last english os .
Could this help
cetuss4 said:
Hello people , I have verge that keeps freezing when receiving several notifications and has sever battery drain. I have factory reset and re-installed the English firmware . But doesn't seem to help.
Will installing the latest Chinese firmware help.
Than I can install the last english os .
Could this help
Click to expand...
Click to collapse
Not sure but you can give it a try.
For this Version
Can change language Chinese >> English without error
Have anybody any news/information when will be official update from Amazfit for Verge (International version) with integrated Alexa or other voice assistant for the rest of the world costumers like: Europe countries and ect?
Can i use NFC function on A1811 with Chinese stock rom?
I heard there are NFC chipsets in A1811 too
Flashing chinese bootloader on A1811 bricks my watch??
vsc0705 said:
Can i use NFC function on A1811 with Chinese stock rom?
I heard there are NFC chipsets in A1811 too
Click to expand...
Click to collapse
No, you can't, AFAIK, but you can give it a shot. I think there is no NFC, since NFC can't be enabled on CN Firmware. There is a dedicated switch for that in the firmware, but it's reported that NFC doesn't turn on for A1811. for A1801 it does.
vsc0705 said:
Flashing chinese bootloader on A1811 bricks my watch??
Click to expand...
Click to collapse
No, it doesn't.
Saratoga79 said:
I think there is no NFC, since NFC can't be enabled on CN Firmware. There is a dedicated switch for that in the firmware, but it's reported that NFC doesn't turn on for A1811. for A1801 it does..
Click to expand...
Click to collapse
NFC is in Verge http://cn.amazfit.com/verge.html before you post asnwer, check information in official web site - it's easy and no need a lot of time :highfive:
As i know NFC will be available later (if talk about US market), why is not activated in China's version i don't know. As i understand NFC is available only for payment process, so everthing maybe working somehow automatic. I can't explain reasons, but as i mentioned web site and others official source saying that NFC is in Verge (Chinese software) and will be later in International (i guest they mean US market only for this moment)
P.S. This is official Amazfit Verge commercial https://www.youtube.com/watch?v=PydD99xx2dk, look what doing guy in commercial from 34 second, he doing payment. Payment process is doing with NFC, what is meantioned in Amazfit web site So yes chinese version must have NFC available, why is not, need to ask Amazfit, but i guest, cos costumers which flashing Chinese ROM is not from China and maybe somehow by GOS is detecting that is not China country and features is not available. It's nonensese probably you will say, but when please explain me why the same software version for International costumers with Alexa working only in US, i got this software with Alexa, but i can't use Alexa, cos i'm not from US, if say exactly i'm not right now in US... I guest in the say working NFC. But maybe i'm wrong
About A1811 i guest you are right, i did not tried, but probably as i mentioned will not works, cos somehow *probably by GPS) this watch is really smart and detecting what you are not in the same market in which these features working If i understand you wrong, sorry, english is no my primary - national language
xdauser2019 said:
NFC is in Verge http://cn.amazfit.com/verge.html before you post asnwer, check information in official web site - it's easy and no need a lot of time :highfive:
As i know NFC will be available later (if talk about US market), why is not activated in China's version i don't know. As i understand NFC is available only for payment process, so everthing maybe working somehow automatic. I can't explain reasons, but as i mentioned web site and others official source saying that NFC is in Verge (Chinese software) and will be later in International (i guest they mean US market only for this moment)
P.S. This is official Amazfit Verge commercial https://www.youtube.com/watch?v=PydD99xx2dk, look what doing guy in commercial from 34 second, he doing payment. Payment process is doing with NFC, what is meantioned in Amazfit web site So yes chinese version must have NFC available, why is not, need to ask Amazfit, but i guest, cos costumers which flashing Chinese ROM is not from China and maybe somehow by GOS is detecting that is not China country and features is not available. It's nonensese probably you will say, but when please explain me why the same software version for International costumers with Alexa working only in US, i got this software with Alexa, but i can't use Alexa, cos i'm not from US, if say exactly i'm not right now in US... I guest in the say working NFC. But maybe i'm wrong
About A1811 i guest you are right, i did not tried, but probably as i mentioned will not works, cos somehow *probably by GPS) this watch is really smart and detecting what you are not in the same market in which these features working If i understand you wrong, sorry, english is no my primary - national language
Click to expand...
Click to collapse
Yes, I know A1801/CN version has NFC, I managed to enable it and I have done some test with 3th party apps but is not usable out of China.
I meant that A1811/International version has no NFC or lacks "something" as flashing Chinese firmware on it NFC doesn't work.
Saratoga79 said:
Yes, I know A1801/CN version has NFC, I managed to enable it and I have done some test with 3th party apps but is not usable out of China.
I meant that A1811/International version has no NFC or lacks "something" as flashing Chinese firmware on it NFC doesn't work.
Click to expand...
Click to collapse
As i know NFC is not just activated yet, if i understand right, coz now is negotiations are under way with markets (probably with companies, where will work services with NFC or something like is, i don't no details), soon must be everything available. But how i mentioned before, probably will works only in US market (like is with Alexa now). Oh well we will see... i hope update will be very soon and maybe with all ours answers
P.S. NFC is microchip which update will not add to watch, so yes NFC is already in yours device, it's just not activated, there is no option to do that yet Keep patience future will show all features... and keep in mind Verge international version is very new, so what you can see in Chinese version, i 'm sure, i hope will be in international version too, just keep waiting patience
Why not working with Chinese software in international version device (A1811 is for all world, except Asia region, as i understand)? I already write my minds, how they are correct i don't know, but idea that not working for reason, coz watch detect somehow (probably by GPS) that you are not in China for me sounds most probable. Why? You got 3.2.20 software update? What was written in it? Alexa that's right? Where is she? Cos working only in US? Are you in US? No, so probably that's reason why is no available for you NFC with Chinese software... But this is just my mind, maybe i wrote totall nonsenses, but i can't to image another reason why with the same software in one market working Alexa in other no, why can't to be the same with NFC and the same software for different market?
By the way are you sure that in Stock CN/Chinese 3.0.29.0 version already was available/activated NFC for China market too? This is second idea which came to head. I really really don't know how Amazfit made software, i mean how it working, so sorry if i wrote something insane, just lound thinking and trying to understand reason